text:
Delay Sought on Iraqi Constitution
According to the AP, the Iraqi Constitutional Committee is seeking a 30-day delay in submitting the Iraqi constitution:
Under the original deadline, the National Assembly had until Aug. 15 to approve the charter and submit it to a national referendum in mid-October. That formula was strongly supported by the Americans. But major differences remain among the ethnic and religious groups represented on the committee.
This will be a serious setback to the American plans (if true, see below). I was told repeatedly all through July that no delay was forthcoming and that the Iraqis should stick to the schedule because, a U.S. official told me, the Iraqis work best under pressure.
"We have consistently urged all members of the national assembly and the Iraqi government to maintain the time schedule outlined in the TAL," he told me in early July. "The press of time is always a factor in Iraqi politics," he continued:
"It was in the Aug. 2004 convening of the national conference, it was again with the preparations for the elections and parties having to make a decision to register and run and their candidates to run. And it will be again, with the constitution. They work best when they're under a time deadline. It makes it harder, but it's just the way diplomacy is here."
"The Americans want to make a quick constitution," said Mahmoud Othman, Kurdish member of the panel, adding that U.S. officials were putting intense pressure on the drafters. However, he cautioned: "They have a lot of experience in fast food, but they can't make a fast constitution."
(Heh. I love Mahmoud. I've sometimes heard other reporters refer to him as "Mr. Dial-a-Quote.")
So this (possible) delay can't be making anyone smile in the embassy today. Especially because I was told by a high-level U.S. diplomat just yesterday that there would be no delay. Further sticking a finger in the eye of the Americans, the issues gumming up the works—federalism and the role of religion—are the same issues that have been bedeviling the process since the get-go. That means the March-to-July frantic behind-the-scenes work of the embassy to broker a consensus has so far borne little fruit. And that further means the American influence is less than most people think.
Although now that I think about it, my conspiratorial mind comes into play. Perhaps everyone has been reading from the same song book—no delay, no way—only to spring the holdup on the Iraqi people at the last minute to make it look like the Iraqis have stood up to the Americans, granting the committee more legitimacy among the people who think it's all being run out of the embassy.
Cunning devils.
But assuming that isn't the case, federalism is probably the main sticking point. The Sunnis don't want any form of federalism because they say it will lead to the breakup of the country, but it's really because they don't [want] the Kurds and Shi'ites to have oil-rich districts with control of the revenues while they get the western desert. I've been out there. It sucks. The Kurds, however, say if they don't get to keep what they have, and Kirkuk, to boot, there's going to be a war.
The role of religion has also been a problem, with the religious Shi'ite parties pushing hard for Islam to be "the main source" of legislation and subordinating the rights of women to shari'ah. There are also some drafts of constitutions floating around enshrining the Shi'ite clergy—the merjariyah, of which Grand Ayatollah Ali al-Sistani is the preeminent member—in a constitutional role, but I don't think that will make it into the final draft.
I'm of two minds on the delay. On the one hand, I don't think a 30-day delay will do much to build trust between the Kurds, Shi'ites and Sunnis, which is the biggest problem affecting Iraq these days. A month isn't enough time for that. On the other hand, perhaps a delay will allow federalism and religion to be crow-barred into position in the document and the trust will just have to come later. Inshallah.
[UPDATE 7:40:36 PM +0300 GMT: Well, well. AFP says non! to the delay, and Reuters says the panel is only "considering" one. At the moment, the U.S. embassy isn't commenting, but there's supposed to be a press conference tomorrow morning. I've not seen a statement from the embassy commenting on the delay yet, so perhaps this thing will be headed off, after all. I'm sure the Americans kicked it into high gear once the committee signaled a willingness to hang the deadline.
[I should have explained it better above, but the deadline for requesting a delay is tomorrow. It's possible that they can ask parliament and the presidency council and have it denied. But if they don't request a delay and can't get the constitution done by Aug. 15, parliament is dissolved and new elections must be called. So the stakes are pretty high.]
Technorati Tags: Baghdad, Current Affairs, News and Politics


text:
hey all, i've created a proposal for my vision of how zones hosted on shared storage should work. if anyone is interested in this functionality then please give my proposal a read and let me know what you think. (fyi, i'm leaving on vacation next week so if i don't reply to comments right away please don't take offence, i'll get to it when i get back. ;)
" please ensure that the vim modeline option is not disabled vim:textwidth=72 ------------------------------------------------------------------------------- Zones on shared storage (v1.0) ---------- A. INTRODUCTION The most commonly requested zones feature is support for the NFS server within a zone (4964859). The next two most requested zones features are support for hosting zones on shared storage, specifically NFS and iSCSI. These last two requests are being tracked via the following bugs: 6688400 Want zonepath on iscsi targets 4963321 RFE: hosting root filesystems for Zones on NFS servers This document proposed a plan to address the latter two issues. These proposed changes will also start to bring the zones storage administration closer in line with the experience provided by other virtualization technologies (VTs, examples of which are xVM, LDOMs, and VirtualBox). ---------- B. BACKGROUND Currently, it is possible to combine existing supported technologies (FC, iSCSI, NFS, lofi, zfs, etc) to host zones on shared storage, and there are a few blog entries out there describing how to create such configurations[00]. While these configurations are usable and technically supportable, they require extensive configuration of multiple different technologies, making them complex, potentially fragile (since they are not regularly tested), and out of reach for most customers. Creating these configurations today also causes problems with the use of other existing zones features, the most obvious of which is zone migration. These configurations complicate zone migration because all of the additional global zone configuration that was required to host the zone on shared storage must be tracked and then migrated along with the zone data itself. VM Migration is critical component of all existing VTs and anything that can be done to improve zone migration support would be a great benifit to zones administrators. All the other virtualization technologies currently available in Solaris support the hosting of Virtual Machines (VMs) on shared storage. They all do this in the same fashion, which involves taking a "storage object"[01] which is accessible from the "global zone"[02], and making it visible within the VM as a local disk. In this document we're refer to this process as "encapsulation", since the "disk" which a VM thinks it's accessing is actually contained (ie encapsulated) within some storage object in the global zone. This encapsulation has advantages and disadvantages. Encapsulation makes it easier to manage the storage associated with VMs. These storage objects may be accessible from multiple hosts simultaneously. They can be backed up, restored, moved around, and copied as individual files instead of filesystems. One disadvantage of the encapsulation used by these other VTs is that currently on Solaris, there is no way to open up these encapsulated disks and access their contents from the global zone. Currently, the only way to access these encapsulated disks is to import them into a running VM. Another interesting development with these encapsulated disks used by other VTs is the proliferation of storage object formats. These custom storage objects formats allows for features which are transparent to the VM using the disks and independent of any features offered by the underlying global zone. While specific feature sets may vary, common features that may be supported are things like compression, sparseness, dedup, snapshotting, and rollback. Management of all these storage object features is usually done from the global zone. Examples of some of these different formats are: VDI - VirtualBox Virtual HDD VHD - Microsoft Virtual Hard Disk VMDK - VMWare Virtual Machine Disk These formats are also commonly used for moving and sharing VM images, and it's not uncommon for users to take VMs encapsulated in one format and convert them into another. ---------- C. PROPOSAL / DESCRIPTION The essence of this proposal is to enhance zonecfg(1m) to allow for the specification of shared storage objects which can be used to encapsulate zone filesystems, including the zones root filesystem. Once shared storage objects are specified in zonecfg(1m) the management of this shared storage will be handled automatically by the zones framework. This will allow administrators to host zones on shared storage with no additional system configuration being required outside of zonecfg(1m). It will also provide zones with a consistent global zone storage usage and administration experience compared with other VTs. All the existing zoneadm(1m) operations that administrators can do today should continue to work seamlessly with this new support for shared storage objects. The proposal is broken down into the following subsections: C.0 Out of scope C.1 Zones enhancements C.2 Storage object uid/gid handling C.3 Taskq enhancements C.4 Zfs enhancements C.5 Lofi and lofiadm(1m) enhancements C.6 Performance considerations C.7 Phased delivery C.8 Future work ---------- C.0 Out of scope Before discussing the details of the changes being proposed, here are the things this proposal will not address: - Hosting zones natively on NFS. We will not be considering enhancements which would allow zone roots to live natively (ie, unencapsulated) on NFS. Supporting this functionality is not prevented by anything proposed herein, but initially we are not pursuing this option because: - Encapsulation allows us to host zones on a myriad of storage in addition to NFS. - Encapsulation brings the zones storage feature set closer in line with other VTs. - Encapsulation will likely be easier to implement than unencapsulated hosting of a zone root filesystems on NFS. - Advanced shared storage configuration. Initially there will be no support for advanced shared storage configuration options. If advanced configuration options need to be used, they will need to be setup in the global zone outside the zones framework. That said, nothing in this proposal should not prevent us from adding support for more complex configurations in the future, should the become popular. Some examples of what would be considered advanced shared storage configuration options are (and this is by no means a complete list): - iSCSI target discovery management - iSCSI target parameter configuration (CHAP, etc) - custom vdisk creation options - encapsulated zpools spanning multiple storage objects - custom zpool/zfs creation options ---------- C.1 Zones enhancements This is a list of proposed enhancements to specific zones subsystems. It is broken down into the following categories: C.1.i Zonecfg(1m) C.1.ii Storage object uri (so-uri) format C.1.iii Zoneadm(1m) install C.1.iv Zoneadm(1m) attach C.1.v Zoneadm(1m) boot C.1.vi Zoneadm(1m) detach C.1.vii Zoneadm(1m) uninstall C.1.viii Zoneadm(1m) clone ---------- C.1.i Zonecfg(1m) The zonecfg(1m) command will be enhanced with the following two new resources and associated properties: rootzpool resource src resource property install-size resource property zpool-preserve resource property dataset resource property zpool resource src resource property install-size resource property zpool-preserve resource property name resource property The new resource and properties will be defined as follows: "rootzpool" - Description: Identifies a shared storage object (and it's associated parameters) which will be used to contain the root zfs filesystem for a zone. "zpool" - Description: Identifies a shared storage object (and it's associated parameters) which will be made available to the zone as a delegated zfs dataset. "src" - Status: Required. - Format: Storage object uri (so-uri). (See definition below.) - Description: Identifies the storage object associated with this resource. "install-size" - Status: Optional. - Format: Integer. Defaults to bytes, but can be flagged as gigabytes, kilobytes, or megabytes, with a g, k, or m suffix, respectively. - Description: If the specified storage object doesn't exist at zone install time it will be created with this specific size. This property has no effect for storage objects which already exist and have a pre-defined size. "zpool-preserve" - Status: Optional. - Format: Boolean. Defaults to false. - Description: When doing an install, if this property if this property is set to true and a zpool already exists on the specified storage object it will be used. When doing a destroy, if this property is set to true, the root zpool will not be destroyed. "dataset" - Status: Optional - Format: zfs filesystem name component (can't contain a '/') - Description: Name of a dataset within the root zpool to delegate to the zone. "name" - Status: Required - Format: zfs filesystem name component (can't contain a '/') - Description: Used as part of the name for a zpool which will be delegated to the zone. Zonecfg(1m) "verify" will verify the syntax of any "rootzpool" resource group (and its properties), but it will NOT verify the accessibility of any storage specified by by a so-uri. (This is because accessing the storage specified by an so-uri could require configuration changes to other subsystems.) ---------- C.1.ii Storage object uri (so-uri) format The storage object uri (so-uri) syntax[03] will conform to the standard uri format defined in RFC 3986 [04]. The nfs URI scheme is defined in RFC 2224 [05]. The so-uri syntax can be summarised as follows: File storage objects: path:///<file-absolute> nfs://<host>[:port]/<file-absolute> Vdisk storage objects: vpath:///<file-absolute> vnfs://<host>[:port]/<file-absolute> Device storage objects: fc:///wwn[@<lun>] iscsi:///alias=<alias>[@<lun>] iscsi:///target=<target>[@<lun>] iscsi://host[:port]/[tpgt=<tpgt>/]target=<target>[@<lun>] File storage objects point to plain files on a local, nfs, or cifs filesystems. These files are used to contain zpools which store zone datasets. These are the simplest types of storage objects. Once created, they have a fixed size, can't be grown, and don't support advanced features like snapshotting, etc. Some example file so-uri's are: path:///export/xvm/vm1.disk - a local file path:///net/heaped.sfbay/export/xvm/1.disk - a nfs file accessible via autofs nfs://heaped.sfbay/export/xvm/1.disk - same file specified directly via a nfs so-uri Vdisk storage objects are similar to file storage objects in that they can live on local, nfs, or cifs filesystems, but they each have their own special data format and varying featuresets, with support for things like snapshotting, etc.. Some common vdisk formats are: VDI, VMDK and VHD. Some example vdisk so-uri's are: vpath:///export/xvm/vm1.vmdk - a local vdisk image vpath:///net/heaped.sfbay/export/xvm/1.vmdk - a nfs vdisk image accessible via autofs vnfs://heaped.sfbay/export/xvm/1.vmdk - same vdisk image specified directly via a nfs so-uri Device storage objects specify block storage devices in a host independant fashion. When configuring FC or iscsi storage on different hosts, the storage configuration normally lives outsize of zonecfg, and the configured storage may have varying /dev/dsk/cXtXdX* names. The so-uri syntax provides a way to specify storage in a host independent fashion, and during zone management operations, the zones framework can map this storage to a host specific device path. Some example device so-uri's are: fc:///20000014c3474...@0 - lun 0 of a fc disk with the specified wwn iscsi:///alias=oracle zone r...@0 - lun 0 of an iscsi disk with the specified alias. iscsi:///target=iqn.1986-03.com.sun:02:38abfd16-78c5-c58e-e629-ea77a33c6740 - lun 0 of an iscsi disk with the specified target id. ---------- C.1.iii Zoneadm(1m) install When a zone is installed via the zoneadm(1m) "install" subcommand, the zones subsystem will first verify that any required so-uris exist and are accessible. If an so-uri points to a plain file, nfs file, or vdisk, and the object does not exist, the object will be created with the install-size that was specified via zonecfg(1m). If the so-uri does not exist and an install-size was not specified via zonecfg(1m) an error will be generated and the install will fail. If an so-uri points to an explicit nfs server, the zones framework will need to mount the nfs filesystem containing storage object. The nfs server share containing the specified object will be auto-mounted at: /var/zones/nfsmount/<zonename>/<host>/<nfs-share-name> If an so-uri points to a fibre channel lun, the zones subsystem will verify that the specified wwn corresponds to a global zone accessible fibre channel disk device. If an so-uri points to an iSCSI target or alias, the zones subsystem will verify that the iSCSI device is accessible on the local system. If an so-uri points to a static iSCSI target and that target is not already accessible on the local host, then the zones subsystem will enable static discovery for the local iSCSI initiator and attempt to apply the specified static iSCSI configuration. If the iSCSI target device is not accessible then the install will fail. Once a zones install has verified that any required so-uri exists and is accessible, the zones subsystem will need to initialise the so-uri. In the case of a path or nfs path, this will involve creating a zpool within the specified file. In the case of a vdisk, fibre channel lun, or iSCSI lun, this will involve creating a EFI/GPT partition on the device which uses the entire disk, then a zpool will be created within this partition. For data protection purposes, if a storage object contains any pre-existing partitions, zpools, or ufs filesystems, the install will fail will fail with an appropriate error message. To continue the installation and overwrite any pre-existing data, the user will be able to specify a new '-f' option to zoneadm(1m) install. (This option mimics the '-f' option used by zpool(1m) create.) If zpool-preserve is set to true, then before initialising any target storage objects, the zones subsystem will attempt to import a pre-existing zpool from those objects. This will allow users to pre-create a zpool with custom creation time options, for use with zones. To successfully import a pre-created zpool for a zone install, that zpool must not be attached. (Ie, any pre-created zpool must be exported from the system where it was created before a zone can be installed on it.) Once the zpool is imported the install process will check for the existence of a /ROOT filesystem within the zpool. If this filesystem exists the install will fail with an appropriate error message. To continue the installation the user will need to specify the '-f' option to zoneadm(1m) install, which will cause the zones framework to delete the pre-existing /ROOT filesystem within the zpool. The newly created or imported root zpool will be named after the zone to which it is associated, with the assigned name being "<zonename>_rpool". This zpool will then be mounted at the zones rootpath and then the install process will continue normally[07]. XXX: use altroot at zpool creation or just manually mount zpool? If the user has specified a "zpool" resource, then the zones framework will configure, initialize, and/or import it in a similar manaer to a zpool specified by the "rootzpool" resource. The key differences are that the name of the newly created or imported zpool will be "<zonename>_<name>". The specified zpool will also have the zfs "zoned" property set to "on", hence it will not be mounted anywhere in the global zone. XXX: do we need "zpool import -O file-system-property=" to set the zoned property upon import. Once a zone configured with a so-uri is in the installed state, the zones framework needs a mechanism to mark that storage as in use to prevent it from being accessed by multiple hosts simultaneously. The most likely situation where this could happen is via a zoneadm(1m) attach on a remote host. The easiest way to achieve this is to keep the zpools associated with the storage imported and mounted at all times, and leverage the existing zpool support for detecting and preventing multi-host access. So whenever a global zone boots and the zones smf service runs, it will attempt to configure and import any shared storage objects associated with installed zones. It will then continue to behave as it does today and boot any installed zones that have the autoboot property set. If any shared sorage objects fail to configure or import, then: - the zones associated with the failed storage will be transitioned to the "uninstalled" state. - an error message will be emitted to the zones smf log file. - after booting any remaning installed zones that have autoboot set to true, the zones smf service will enter the "maintainence" state, there by prompting the administrator to look at the zones smf log file. After fixing any problems with shared storage accessibility, the admin should be able to simply re-attach the zone to the system. Currently the zones smf service is dependant upon multi-user-server, so all networking services required for access to shared storage should be propertly configured well before we try to import any shared storage associated with zones. On system shutdown, the zones system will NOT export zpools contained within storage object used by the zone. Zpools contained within storage objects assigned to installed zones will only be exported during zone detach. More details about the behaviour of zone detach is provided below. ---------- C.1.iv Zoneadm(1m) attach The zoneadm(1m) attach operation moves a zone from the configured to the installed state. This operation will behave similarly to to a zoneadm(1m) install wrt so-uri management. One key difference between attach and install is that during an attach, any missing storage objects will not be automatically created and instead the attach will fail. Once all the storage objects associated with an attaching zone are configured and accessible, the attach operation will attempt to import and mount the zpools contained within those storage objects. If zfs detects that any zpools are in use by another host the attach will fail. A new '-f' option will be added to zoneadm(1m) which will allow the user to force import and mount any zpools which appear to still be in use. (once again, this option mimics the '-f' option used by zpool(1m) import.) Currently, when a zone is attached to a system a software inventory check is done to verify that the contents of the zone are in sync with the global zone. If they are then the zone is successfully attached. If the contents are older than what is present in the global zone, then the attach fails unless the user specifies the "-u" update option. If the contents of the zone are newer than what is in the global zone then the attach will fail. Encapsulated zones within zpools changes the behaviour of attach slightly because if the zone was created on a host with newer global zone bits, it's possible that the zpool/zfs filesystem versions associated with that zpool may be newer than what the host supports. If this is the case we will be unable to import the zone to check it's software contents. In practice this is not a problem because we know that if the zpool/zfs versions used by an encapsulated zone are later than that supported by the global zone, the software contents of that zone are also guaranteed to be later than what we have in our global zone, so the attach would fail regardless. In the case of older zpool/zfs encapsulated zpool versions, these can be imported without a problem and the version numbers will remain unchanged by the attach operation. ---------- C.1.v Zoneadm(1m) boot The "dataset" property within a "rootzpool" is designed to provide a convenient mechanism for zones to store data within the root zpool, but outside of the /ROOT filesystem (which is subject to snapshotting and cloning during boot environment management operations). To keep things simple, the dataset property can only specify a single path component. (ie, it can not contain any '/' characters.) If the user has specified the "dataset" property for a "rootzpool" resource, then when the zone is booted the framework will check for the presence of a zfs filesystem named /dataset/<dataset> within the root zpool. If no such filesystem exists it will be created. If this zfs filesystem is created by the zones framework, it will have the zfs mountpoint property set to none. This filesystem will then be be delegated to the zone as if a zonecfg(1m) "dataset" resource with a name property value set to "<zonename>_rpool/dataset/<dataset>" existed. For example, if a admin want to configure a zone contained within a single storage object, but still have a seperate dataset where they can manage snapshots and clones of their data independantly of their root filesystem and software, then they could create a configuration as follows: ---8<--- zonecfg -z ibis ... add rootzpool set src=iscsi:///alias=ibis z...@0 set dataset=oracle_data end ---8<--- once this zone was booted, the zone would have access to the following zfs dataset: ibis_rpool/dataset/oracle_data, and it could mount, snapshot, and clone this dataset. all independantly of any zone ROOT dataset snapshots and clones created by system management tools, image-updates, etc. If a zone has any "zpool" resources specified, when the zone is booted those zpools will be delegated to the zone. ---------- C.1.vi Zoneadm(1m) detach The zoneadm(1m) detach operation will be enhanced so that when detaching a zone from a system, any zpools residing in storage objects associated with the detaching zone will be exported. This will allow the administrator to attach the zone on another host without having to specify the force flag ('-f') to zoneadm(1m) attach. Also, if any static iSCSI storage objects are associated with the zone, the iSCSI initiator configuration for those targets will be removed. (Although iSCSI initiator static discovery will remain enabled.) ---------- C.1.vii Zoneadm(1m) uninstall If a user initiates a zoneadm(1m) uninstall operation, then for each zpool specified via a "rootzpool" or "zpool" resource, if the "zpool-preserve" property is set to false, the zpool contained within the specified storage object will be destroyed. If the "zpool-preserve" property is set to true, then for a "rootzpool" resource only the /ROOT filesystem (and any of it's descendents) within the root zpool will be destroyed, and then all the zones zpools will be exported. After destroying or exporting the zpool, any associated storage object will be unconfigured as described in the zoneadm(1m) detach section above. ---------- C.1.viii Zoneadm(1m) clone Normally when cloning a zone which lives on a zfs filesystem the zones framework will take a zfs(1m) snapshot of the source zone and then do a zfs(1m) clone operation to create a filesystem for the new zone which is being instantiated. This works well when all the zones on a given system live on local storage in a single zfs filesystem, but this model doesn't work well for zones with encapsulated roots. First, with encapsulated roots each zone has it's own zpool, and zfs (1m) does not support cloning across zpools. Second, zfs(1m) snapshotting/cloning within the source zpool and then mounting the resultant filesystem onto the target zones zoneroot would introduce dependencies between zones, complicating things like zone migration. Hence, for cloning operations, if the source zone has an encapsulated root, zoneadm(1m) will not use zfs(1m) snapshot/clone. Currently zoneadm(1m) will fall back to the use of find+cpio to clone zones if it is unable to use zfs(1m) snapshot/clone. We could just fall back to this default behaviour for encapsulated root zones, but find+cpio are not error free and can have problem with large files. So we propose to update zoneadm(1m) clone to detect when both the source and target zones are using separate zfs filesystems, and in that case attempt to use zfs send/recv before falling back to find+cpio. Today, the zoneadm(1m) clone operations ignores any additional storage (specified via the "fs", "device", or "dataset" resources) that may be associated with the zone. Similarly, the clone operation will ignore additional storage associated with any "zpool" resources. Since zoneadm(1m) clone will be enhanced to support cloning between encapsulated root zones and un-encapsulated root zones, zoneadm(1m) clone will be documented as the recommended migration mechanism for users who which to migrate existing zones from one format to another. ---------- C.2 Storage object uid/gid handling One issue faced by all VTs that support shared storage is dealing with file access permissions of storage objects accessible via NFS. This issue doesn't affect device based shared storage, or local files and vdisks, since these types of storage are always accessible, regardless of the uid of the access process (as long as the accessing process has the necessary privileges). But when accessing files and vdisk via NFS, the accessing process can not use privileges to circumvent restrictive file access premissions. This issue is also complicated by the fact that by default most NFS servier will map all accesses by remote root user to a different uid, usually "nobody". (a process known as "root squashing".) In order to avoid root squashing, or requiring users to setup special configurations on their NFS servers, whenever the zone framework attempts to create a storage object file or vdisk, it will temporarily change it's uid and gid to the "xvm" user and group, and then create the file with 0600 access permissions. Additionally, whenever the zones framework attempts to access an storage object file or vdisk it will temporarily switch its uid and gid to match the owner and group of the file/vdisk, ensure that the file is readable and writeable by it's owner (updating the file/vdisk permissions if necessary), and finally setup the file/vdisk for access via a zpool import or lofiadm -a. This should will allow the zones framework to access storage object files/vdisks that we created by any user, regardless of their ownership, simplifying file ownership and management issues for administrators. ---------- C.3 Taskq enhancements The integration of Duckhorn[08] greatly simplifies the management of cpu resources assigned to zone. This management is partially implemented through the use of dynamic resource pools, where zones and their associated cpu resources can both be bound to a pool. Internally, zfs has worker threads associated with each zpool. These are kernel taskq threads which can run on any cpu which has not been explicitly allocated to a cpu set/partition/pool. So today, for any zones living on zfs filesystems, and running in a dedicated cpu pool, any zfs disk processing associated with that zone is not done by the cpu's bound to that zones pool. Essentially all the zones zfs processing is done for "free" by the global zone. With the introduction of zpools encapsulated within storage objects, which are themselves associated with specific zones, it would be desirable to have the zpool worker threads bound to the cpus currently allocated to the zone. Currently, zfs uses taskq threads for each zpool, so one way of doing this would be to introduce a mechanism that allows for the binding of taskqs to pools. Hence we propose the following new interfaces: zfs_poolbind(char *, poolid_t); taskq_poolbind(taskq_t, poolid_t); When a zone, which is bound to a pool, is booted, the zones framework will call zfs_poolbind() for each zpool associated with an encapsulated storage object bound to the zone being booted. Zfs will in turn use the new taskq pool binding interfaces to bind all it's taskqs to the specified pools. This mapping is transient and zfs will not record or persist this binding in any way. The taskq implementation will be enhanced to allow for binding worker threads to a specific pool. If taskqs threads are created for a taskq which is bound to a specific pool, those new thread will also inherit the same pool bindings. The taskq to pool binding will remain in effect until the taskq is explicitly rebound or the pool to which it is bound is destroyed. ---------- C.4 Zfs enhancements In addition to the zfs_poolbind() interface proposed above. The zpool(1m) "import" command will need to be enhanced. Currently the zpool(1m) import by default scans all storage devices on the system looking for pools to import. The caller can also use the '-d' option to specify a directory within which the zpool(1m) command will scan for zpools that may be imported. This scanning involves sampling many objects. When dealing with zpools encapsulated in storage objects, this scanning is unnecessary since we already know the path to the objects which contains the zpool. Hence, the '-d' option will be enhanced to allow for the specification of a file or device. The user will also be able to specify this option multiple times, in case the zpool spans multiple objects. ---------- C.5 Lofi and lofiadm(1m) enhancements Currently, there is no way for a global zone to access the contents of a vdisk. Vdisk support was first introduced in VirtualBox. xVM then adopted the VirtualBox code for vdisk support. With both technologies, the only way to access the contents of a vdisk is to export it to a VM. To allow zones to use vdisk devices we propose to leverage the code introduced by by xVM by incorporating it into lofi. This will allow any solaris system to access the contents of vdisk devices. The interface changes to lofi to allow for this are fairly straitforward. A new '-l' option will be added to the lofiadm(1m) "-a" device creation mode. The '-l' option will indicate to lofi that the new device should have a label associated with it. Normally lofi device are named /dev/lofi/<I> and /dev/rlofi/<I>, where <I> is the lofi device number. When a disk device has a label associated with it, it exports many device nodes with different names. Therefore lofi will need to be enhanced to support these new device names, which multiple nodes per device. These new names will be: /dev/lofi/dsk<I>/p<j> - block device partitions /dev/lofi/dsk<I>/s<j> - block device slices /dev/rlofi/dsk<I>/p<j> - char device partitions /dev/rlofi/dsk<I>/s<j> - char device slices A new '-v <vdisk-format>' option will be added to the lofiadm(1m) "-a" device creation mode. This will indicate to lofi that the new device which is being created will be stored within a vdisk instead of a normal file. Vdisk formats may provide their own management features such as snapshotting, compression, encryption, etc. As such, the lofi vdisk support exists purely to access the contents of vdisks. Hence, vdisk based lofi devices will not support other lofi options such as encryption ('-c') and compression ('-C' / '-U'). Also, all vdisks contain actually disks, so they all contain a partition/label data. hence when attaching a vdisk the '-l' flag is always implied (and should not be specified.) The vdisk formats that will be supported by lofi are whatever vdisk formats happen to be supported by xVM at the time of integration. Since the implementation between lofi and xVM will be shared, as new vdisk format support is added to xVM, it should be immediately supportable via lofi as well. The current xVM implementation for accessing vdisks involves two drivers and a userland utility. A "frontend" driver runs inside a VM and it exports normal solaris disk interface. It takes IO requests to these disks and transmits them, via a ring buffer, to the "backend" driver running in the global zone. The backend driver then maps these ring requests into a dedicated vdisk process (there is one such process for every vdisk), and this process translates these ring requests into access to a vdisk of the requested format. Given all this existing xVM functionality, the most straitforward way to support vdisk from within lofi would be to leverage the xVM implementation. This will involve re-factoring the existing xVM code, thereby allowing lofi to utilise the "frontend" code which translates strategy io requests into ring buffer requests, and also the "backend" code which exports the ring buffer to userland. The unchanged xVM userland vdisk utility can then be used to map ring buffer requests to the actual vdisk storage. Currently this utility is only available on x86, but since lofi is a cross-platform utility, this proposal will require the delivery of this utility on both sparc and x86. This utility is currently delivered in an xVM private directory, /usr/lib/xen/bin/vdisk. Given that lofi is a more general and cross platform utility as compared to xVM, and also given that that we don't expect users to access the vdisk management utilities directly, we propose to move the vdisk application to /usr/lib/lofi/bin/vdisk. For RAS purposes, we will need to ensure that this vdisk utility is always running. Hence we will introduce a new lofi smf service svc:/system/lofi:default, which will start a new /usr/lib/lofi/lofid daemon, which will manage the starting, stopping, monitoring, and possible re-start of the vdisk utility. Re-starts of vdisk utility should be transparent (aside from a short performance hiccup) to any zones accessing those vdisks. By default this service will be disabled. If a lofi vdisk device is created, this service will be temporarily enabled. When the last vdisk based lofi device is destroyed, this service will disable itself. XXX: what to do about disk geometry assignment? sigh. Here's some examples of how this lofi functionality could be used (outside of the zone framework). If there are no lofi devices on the system, and an admin runs the following command: lofiadm -a -l /export/xvm/vm1.disk they would end up with the following device: /dev/lofi/dsk0/p# - for # == 0 - 4 /dev/lofi/dsk0/s# - for # == 0 - 15 /dev/rlofi/dsk0/p# - for # == 0 - 4 /dev/rlofi/dsk0/s# - for # == 0 - 15 If there are no lofi devices on the system, and an admin runs the following command: lofiadm -a -v /export/xvm/vm1.vmdk they would end up with the following device: /dev/lofi/dsk0/p# - for # == 0 - 4 /dev/lofi/dsk0/s# - for # == 0 - 15 /dev/rlofi/dsk0/p# - for # == 0 - 4 /dev/rlofi/dsk0/s# - for # == 0 - 15 By default, format(1m) will not list these devices in it's output. But users will be able to treat these devices like regular disks and pass their names to utilities like fdisk(1m), format(1m), prtvtoc(1m), fmthard(1m), zpool(1m), etc. ---------- C.6 Performance considerations As previously mentioned, this proposal primarily simplifies the process of configuring zones on shared storage. In most cases these proposed configurations can be created today, but no one has actually verified that these configurations perform acceptably. Hence, in conjunction with providing functionality to simplify the setup of these configs, we also need to be quantifying their performance to make sure that none of the configurations suffer from gross performance problems. The most straitforward configurations, with the least possibilities for poor performance, are ones using local devices, fibre channel luns, and iSCSI luns. These configuration should perform identically to the configurations where the global zone uses these objects to host zfs filesystems without zones. Additionally, the performance of these configurations will mostly be dependent upon the hardware associated with the storage devices. Hence the performance of these configuration is for the most part uninteresting and performance analysis of these configuration can by skipped. Looking at the performance of storage objects which are local files or nfs files is more interesting. In these cases the zpool that hosts the zone will be accessing it's storage via the zpool vdev_file vdev_ops_t interface. Currently, this interface doesn't receive as much use and performance testing as some of the other zpool vdev_ops_t interfaces. Hence it will worthwhile to measure the performance of a zpool backed by a file within another zfs filesystem. Likewise we will want to measure the performance of a zpool backed by a file on an NFS filesystem. Finally, we should compare these two performance points to a zone which is not encapsulated within a zpool, but is instead installed directly on a local zfs filesystem. (These comparisons are not really that interesting when dealing with block device based storage objects.) Currently, while it is very common to deploy large numbers of zfs filesystems, systems with large numbers of zpools are not very common. The solution proposed in this project will likely result in an increase of zpools on systems hosting zones. Hence, we should evaluate the impact of an increasing number of zpools on performance scalability. This could be done by comparing the io performance drop-off of an increasing number of zones hosted multiple zfs filesystems in a single zpool vs zones hosted in seperate zpools. Finally, it will be important to do performance measurements for vdisk configurations. These configurations are similar to the local file or nfs configurations, but they will be utilising the vdev_disk backend and they will have an additional layer of indirection through lofi. XXX: impact of multiple zpools on arc and l2 arc? talk to mark maybee. ---------- C.7 Phased delivery Customers have been asking for a simple mechanisms to allow hosting of zones on NFS since the introduction of zones. Hence we'd like to get this functionality into the hands of customers as quickly as possible. Also, the approach taken by this proposal to supporting zones on shared storage is different from what was originally anticipated, hence we'd like to get practical experience with this approach at customer sites asap to determine if there are situations where this approach may not meet their requires. To accelerate the delivery of the previously proposed features, we plan to deliver them in three phases: I - Basic Zone encapsulation support This will involve the introduction of the new "rootzpool" and "zpool" resources and support the "file" and "nfs" type storage objects. It will require implementation of all the proposed zone, zfs, and taskq changes. This phase will not require any lofi changes. II - Zone encapsulation on fc and iSCSI storage. This will provide enhanced so-uri support for fibre channel and iSCSI type storage objects. III - Zone encapsulation on vdisk storage. This will involve implementation of the proposed lofi enhancements and enhancement support for vdisk type storage objects. ---------- C.8 Future work In addition to the proposed work above, there are future enhancements that could be made which would extend the functionality proposed above. These are included here because the features proposed above have been designed with this extensibility in mind. One simple enhancement would be the addition a new "rootzpool/zpool" resource property called "zpool-auto-upgrade". If set to true, whenever a zpool is imported by the zones framework (at install, attach, or boot) the zpool and zfs filesystems would be upgraded to the latest version supported by the global zone. Aside from helping to ensure that zones are using the latest and greatest zpool/zfs features, this feature would help ensure that all the encapsulated zones on a system are running on the same zpool/zfs versions. This is important because zfs send and receive are not guaranteed to be compatible across zpool/zfs versions. So by ensure that all zones are running the latest zpool/zfs versions, we increase the chances of being able to use zfs send/recv for zone cloning. Another possible enhancement to the "rootzpool/zpool" resources would be to allow the specification of multiple so-uris to support more complex root zpool configurations. With the introduction of vdisk support, we will have the ability to access VMs created by other VTs. Using this functionality it would be straitforward to enhance the existing zoneadm(1m) attach p2v functionality to be able to do v2v, where the source system image for installing a zone could be a vdisk created by another VT. Finally, a new "storage" zonecfg(1m) resource could be added to allow for the addition of arbitrary storage objects to zones. This "storage" resource would have the similar properties as a "zpool" resource, along with a few additional properties: storage resource src resource property install-size resource property name resource property locking-required resource property The zones framework would ensure that the specified storage objects were accessible from the global zone, and then it would grant the zone access to the raw disk devices. But global zone disk device names can be different on different host, so if global zone device names were used within the non-global zone, this would negatively impact zone migration since the software within the zone would have to be updated to deal with potentially new device names. To avoid this problems and factilitate zone migration, the disk devices would be mapped into the non-global zone with different names which would be global zone independant. Regadless of the global zone disk device name, from within the non-global zone, the devices would be named: /dev/storage/<name>/p<j> /dev/storage/<name>/s<j> By basing the names of the device as seen from within the zone on the "name" specified in the zonecfg(1m) (instead of the raw device names from the global zone), we can guarantee that these device names will not change when migrating the zones between hosts. One difficulty with allowing the specification of storage objects which don't by default contain a zpools is that we can no longer use zfs to ensure that multiple entities are not accessing these objects at the same time. Hence other mechanisms will need to be used. In the case of fibre channel and iSCSI, we should be able to use SCSI reservations. In the case of file paths we should be able to use standard file locking. In the case of vdisks, some vdisks support meta-data which can be utilised to prevent concurrent access, and if a vdisk format does not allow for this then we will need to fall back to file locking. If for some reason we are unable to do in use detection for a specific storage object, then we could alert the user and refuse to use that storage object unless the user set the optional "locking-required" property to false. ---------- D. INTERFACES Zonecfg(1m): rootzpool committed, resource src committed, resource property install-size committed, resource property zpool-preserve committed, resource property dataset committed, resource property zpool resource src resource property install-size resource property zpool-preserve resource property name resource property Zoneadm(1m): install -f committed, optional flag attach -f committed, optional flag Zones misc: /var/zones/nfsmount/<zonename>/<host>/<nfs-share-name> project private, nfs mount point Taskq pool binding: taskq_poolbind(taskq_t, poolid_t) consolidation private Zfs pool binding: zfs_poolbind(char *, poolid_t) consolidation private Lofiadm(1m): -a -l committed, optional flag -a -v <vdisk-format> committed, optional flag Lofi misc: svc:/system/lofi:default project private /lib/lofi/lofid project private /lib/lofi/vdisk consolidation private /w contract for xVM ---------- E. ABBREVIATIONS VDI - VirtualBox Virtual HDD VHD - Microsoft Virtual Hard Disk VM - Virtual Machine VMDK - VMWare Virtual Machine Disk VT - Virtualization Technology ---------- F. FOOTNOTES / REFERENCES -- 00 - Blogs and emails describing custom configurations used to host zones on shared storage: June 2005 Containers on NFS? http://blogs.sun.com/jph/entry/containers_on_nfs February 2008 The quick & dirty guide to zones on iSCSI LUNs http://opensolaris.org/jive/thread.jspa?messageID=226951 April 2008 ZoiT: Solaris Zones on iSCSI Targets (aka NAC: Network-Attached Containers) http://blogs.sun.com/JeffV/entry/zoit_solaris_zones_on_iscsi -- 01 - For the purposes of this document, the term storage object refers to any device or file which can be used to store data. These "objects" can take the form of files on a local filesystem, files on a remote filesystem accessible via NFS, CIFS, etc, local disk devices, FC disk devices, iSCSI target devices, -- 02 - Each VT has a different name for the zones concept of the "global zone". With LDOMs we have the "control domain", with xVM we have "dom0", with VirtualBox we have the "host domain". For the purposes of this document the "global zone" refers to the OS entity which allocates resources to and has control over the state of VMs. For simplicity, this document will always just refer to the "global zone" in place of all these other terms. -- 03 - Complete so-uri ABNF syntax definition: so-uri = path-uri / nfs-uri / vpath-uri / vnfs-uri / fc-uri / iscsi-uri path-uri = "path://" file-absolute file-absolute = "/" *( segment "/" ) segment-nz ; Since file-absolute is always the last component ; in a uri reserved characters do not need to be ; percent encoding. nfs-uri = "nfs://" hostport "/" file-absolute ; Defined in RFC 2224 [05] hostport = host [ ":" port ] vpath-uri = "vpath://" file-absolute vnfs-uri = "vnfs://" host [ ":" port ] "/" file-absolute ; same syntax as nfs-uri fc-uri = "fc:/// wwn [ "@" lun ] wwn = 1000 12HEXDIG / 2 15HEXDIG / 50 14HEXDIG / 60 14HEXDIG ; see http://en.wikipedia.org/wiki/World_Wide_Name iscsi-uri = "iscsi:///" iscsi-alias / "iscsi:///" iscsi-target / "iscsi://" iscsi-static iscsi-alias = "alias=" iscsi-alias-name [ "@" lun ] iscsi-alias-name = 1*255pchar ; Defined in RFC 3720 [06] ; any "@" chars must be percent encoded iscsi-target = "target=" iscsi-target-iqn [ "@" lun ] / "target=" iscsi-target-eui [ "@" lun ] iscsi-target-iqn = "iqn." iqn-date "." reg-name [ ":" 1*pchar ] ; Defined in RFC 3720 [06] ; any "@" chars must be percent encoded iqn-date = 4DIGIT "-" "0" %x31-39 ; "XXXX-01" - "XXXX-09" / 4DIGIT "-" "1" %x30-32 ; "XXXX-10" - "XXXX-12" iscsi-target-eui = XXX ; Defined in RFC 3720 [06] ; any "@" chars must be percent encoded iscsi-static = hostport "/" [ "tpgt=" iscsi-tpgt "/" ] iscsi-target iscsi-tpgt = DIGIT ; 0-9 / %x31-39 1*3DIGIT ; 10-9999 / %x31-35 4DIGIT ; 10000-59999 / "6" %x30-34 3DIGIT ; 60000-64999 / "65" %x30-34 2DIGIT ; 65000-65499 / "655" %x30-32 1DIGIT ; 65500-65529 / "6553" %x30-35 ; 65530-65535 lun = DIGIT ; 0-9 / %x31-39 1*3DIGIT ; 10-9999 / "1" %x30-35 3DIGIT ; 10000-15999 / "16" %x30-32 2DIGIT ; 16000-16299 / "163" %x30-37 1DIGIT ; 16300-16379 / "1638" %x30-33 ; 16380-16383 DIGIT = Defined in RFC 3986 [04] HEXDIG = Defined in RFC 3986 [04] segment-nz = Defined in RFC 3986 [04] segment = Defined in RFC 3986 [04] host = Defined in RFC 3986 [04] port = Defined in RFC 3986 [04] -- 04 - RFC 3986: Uniform Resource Identifier (URI): Generic Syntax http://www.ietf.org/rfc/rfc3986.txt http://www.websitedev.de/temp/rfc3986-check.html.gz -- 05 - RFC 2224 NFS URL Scheme http://www.ietf.org/rfc/rfc2224.txt -- 06 - RFC 3720: Internet Small Computer Systems Interface (iSCSI) -- 07 - Zones/SNAP Design - 8/25/2008 http://www.opensolaris.org/jive/thread.jspa?messageID=272726񂥖 -- 08 - PSARC/2006/496 Improved Zones/RM Integration http://arc.opensolaris.org/caselog/PSARC/2006/496 -------------------------------------------------------------------------------
_______________________________________________ zones-discuss mailing list email@example.com

subset: commoncrawl


text:
Do you ever feel like you have regained your sight about a situation? Maybe it is what you wanted to realize, maybe not. But God will help us see, He will carry us. That is all the more reason to follow and glorify!
Do you ever feel like you have regained your sight about a situation? Maybe it is what you wanted to realize, maybe not. But God will help us see, He will carry us. That is all the more reason to follow and glorify!
Ask for peace, joy, hope, strength, healing, forgiveness–bring it Christ, bring it to your adversaries, and know.
We spent a week at a lake in northern Minnesota in August. We were unplugged, and in a remote area, so saw few boats or people. It was a perfect lake for fishing and relaxing. I finally understood what people mean when they say they feel closer to God fishing than anywhere else. I floated out on the paddleboard on Sunday morning, staring into the water, staring up at the sky, and prayed and talked with God for over an hour. Praises, gratitude, hopes, worries. I truly felt His spirit. It reminded me of all the passages in the Bible to BE STILL. The perfect stillness of the nature and lake was anything but empty. We drove away after that week discussing how we can get back, how we could be there permanently. But it wasn't that lake, it was that stillness in Christ. We just have to look for ways to get it in our regular life as well.
This art was inspired by this song by King and Country. I have liked this song for awhile and when I finally watched the video, I liked it even more. It is a commentary on how much our news media portrays everything with doom and gloom, when our days are filled with wonderful moments of joy all the time, if we use our perspective to see it that way. And that joy comes from the hope Christ gives us, the gratitude in recognizing that, and the love that fills us.
Listen to this song by Ryan Stephenson
This is the lyric video, so you can follow along with the amazing words. And I created this in response:
Look forward to our future in Christ. Look forward to eternal life with Him. Do not look this way or that, but stare straight into the path God has for you.


text:
In 1964, Ivo Lapenna became president of Universal Esperanto Association. The law professor, Croatian by birth and then living in London, was a charismatic leader who wanted to bring the Esperanto movement forward by extensive outreach. For that he was not shy of spending some money of the association and try something at UNESCO, the UN organization for education, science and culture.
By then, UEA was in 'consulting relations' with UNESCO, as where many other non governmental organizations. In 1954 UNESCO had recognized the accomplishments of the Esperanto movement for international understanding. Now Ivo Lapenna wanted UNESCO to tell the member states that they introduce Esperanto as a foreign language in schools.
For this proposal UEA and its ten thousands of members collected ultimately nearly one million signatures of individuals and signatures of the representatives of 3,800 organizations. In October 1966, a delegation led by Lapenna visited the UN vice secretary Chakravarthy Narasimhan to hand over the most important signatures.
Mr. Narasimhan explained that only member states can add the question of Esperanto as a school subject to the agenda of the general assembly. Lapenna mentioned a paragraph in the rules of procedure that the UN secretary himself can add an item to the agenda. Mr. Narasimhan answered that that relates only to matters concerning the secretary, e.g. the UN construction in New York.
Lapenna insisted that the rights of the secretary are 'not limited' and that 'being a professor of international law I know certainly what is UN and what are the powers of the different organs.' Lapenna wanted the vice secretary to send at least an official UN communiqué to the member states about the Esperanto proposal. None of this happened, in spite of some angry letters by Lapenna the following years and his complains about 'linguistically privileged' UN officials and their sabotage.
Looking back, I asked a former collaborator of UEA what to make up of the petition of the 1960s – pricy in years when the association suffered some severe financial shortcomings. The collaborator explained that Lapenna was never so naive that he believed he could get through with it. But Lapenna wanted to have a subject to tell about to the press, and something to mobilize the Esperanto speakers and have them occupied with. And of course, one might add, to show that Lapenna was a capable and agile leader.
(Ziko van Dijk: 1966: Propono al UN. Kial Lapenna ne farigxis la heroo de Novjorko. In: (the same) La Asocio. Skizoj kaj studoj pri la historio de UEA. Flandra Esperanto-Ligo, Antwerp 2008, pp. 277-287.)


text:
Bare Conductive Paint is a multipurpose electrically conductive material perfect for all of your DIY projects! Bare Paint is water based, nontoxic and dries at room temperature.
Bare Paint is the first non-toxic electrically conductive paint available to consumers today. This unique child-friendly material is designed for people of all ages to explore and learn about electronics with an inclusive, easy-to-use material.
Bare Paint provides a dramatically different method of interacting with electronics as it can be applied to almost any surface, including cardboard, paper, wood, wallpaper, walls, textiles, and some plastics.
Bare paint can be used to replace conventional acid etching, making it a great electronics prototyping tool. Nontoxic and water-soluble, Bare Paint can be used without gloves or mask. The paint dries quickly at room temperature, and can be removed with soap and water. This means it's also not water-proof or weather-resistant!
Application Methods Include: painting, screen printing & spray painting among others. Despite being called "Bare" conductive, it's meant not for use on bare skin.
Bare Conductive Paint Pen - 10mL (8:29)
Technical Details
- 10 mL pen
- Datasheet with much more information including resistivity
- Weight: 15.67g
Bare conductive has many tutorials showing usage examples on their site
For Bare Conductive product support, email them at [email protected]
This product is listed in:
Documentation and Resources:
- The Maker Revolution
The Maker Revolution celebrates the creation of new devices and the modification of existing ones - the transition from a consumer buying goods to eventually having a major part in their creation. The Maker Revolution places strong emphasis on free (...
Tags: infographic maker movement poster revolution
Product Comments
Exact shipping can be calculated on the view cart page (no login required).
We deliver Australia-wide with these options:
- $3 for Small Items (3-7 days, not tracked, only available on selected small items)
- $6.95 for Standard Post (2-4 days, tracked)
- $9.95 for Express Post (Overnight for most of Australia, 2+ days for rural, tracked)
- Pickup - Free! Only available to customers who live in the Newcastle region (only after we email you to notify your order is ready)
International Orders - the following rates are for New Zealand and will vary for other countries:
- $11.49 for Pack and Track (3+ days, tracked)
- $16.50 for Express International (2-5 days, tracked)
If you order lots of gear, the postage amount might increment based on the weight of your order.
Our physical address (here's a PDF which includes other key business details):
Unit 18, 132 Garden Grove Parade
Take a look at our customer service page if you have other questions such as "do we do purchase orders" (yes!) or "are prices GST inclusive" (yes they are!). We're here to help - get in touch with us to talk shop.


text:
In the Easter holidays about sixty members of our school set out on an expedition for the Duke of Edinburgh Award, otherwise known as D of E. I was in a group of seven, and we begun our journey in high spirits. We had completed our practice expedition in October, and now we were undertaking the real expedition. On the practice I borrowed my mother's shoes and, unfortunately, they were too small – by the end of the first day of hiking I had Hematoma under my big toe. Hematoma/Haematoma is an accumulation of blood in a certain place, like a bruise, but it hurts a lot more! And so on top of the mountain I had to cut my toenails using one of the teacher's penknives. Then proceeded one of the most horrible experiences of my life: the school doctor had to drill a hole through my toenail (sorry to be so graphic) so that the blood could squirt out. To make matters worse, I still had to finish the walk in excruciating pain.
I knew not to make the same mistake at Easter, so the week before the expedition I bought myself some new hiking shoes, and I was determined that they would not be too small. And so, in my new boots and in the cold weather, we set out on the first day of our D of E hike. We had to walk about 23 kilometres each day for three days – that amounts to about 70 kilometres with no day between to rest. And there was me thinking Bronze D of E (only 13 kilometres for two days) was hard! All of the other hikers that we passed were very kind and indeed many stopped to chat to us. One man, I remember, asked where we were staying. When we told him, he began to giggle: it was only then that we discovered the weather forecast. A huge dump of snow was forecasted that night, and it was to fall right where our campsite was!
And as we settled down for the night in our tents, we prayed that it would not snow and that we would stay warm. However alas! It was not so. I was awoken in the night by the shouts of one of my teachers:
"Is everybody okay? Who's in here? Are you alright?"
"Y-y-y-yes sir-r-r-r" I replied, shivering.
He had been rung in the night by one of the girl's tents requesting that he pick them up and 'save them'. The girls were taken to sleep in the toilets, which were somewhat warmer, and typically, all the boys pretended not to be cold, so that no one person would be branded a coward. And so we soldiered on through the night, shivering and burying ourselves in our sleeping bags.
As I pulled down the zipper of my tent, I saw to my horror that my backpack had been entombed under piles of snow, even though it was under part of the tent! Eager to see the mark left by the snow, I crawled out of my tent and couldn't believe my eyes. A carpet of snow had encompassed everything in site, and there was no inch left uncovered. A few minutes after I had arisen some teachers arrived, ordering us to pack up the girl's tents and bags – they had failed their expedition. In the blistering cold, with no gloves, this was indeed a horrible experience. The metal poles of the tents stuck to my fingers and froze my skin! On top of this, we had to pack up our own tents and bags in anticipation of our day's walk.
However, just as we were preparing to set off, our assessor broke the news to us: our expedition had to be called off. It was not safe to make us walk during the blizzard, and there was no other way we could complete it. And so we had endured an entire day of hiking for nothing. Not only that, but we had also completed 30 hours of Volunteering, amongst other things, just to have failed our award – it had all been wasted!
But it was not all bad! Luckily our teachers were able to organise a second internally assessed expedition at the beginning of the summer holidays. Although I had to sacrifice 3 days of my holiday, I thought it was worth it, rather than all my hard work having gone to waste. Nevertheless, we still lost one of the members of our group who wasn't eager to go on another expedition, which was a very traumatic experience for us all.
And so again we set off, after we had completed our GCSEs and were starting to relax for summer. However I never fully relaxed until the expedition was over as it was looming over me for the first week of summer. In slightly less high spirits our expedition begun, and let me just say that for me, my spirits did not improve. In fact they steadily plummeted throughout the walk. On the first day I managed to twist my right ankle while stumbling through a quarry while my entire group were about a hundred metres ahead of me.
It then became almost unbearable to walk, and so I devised a way to travel the distance in the least amount of pain: this was only possible if I steadily jogged without lifting my feet very high from the ground, so that each step was very light. However as you can guess this was very tiring, and made almost impossible by my twisted ankle. My group seemed to find my plight exceedingly hilarious, making the experience all the more horrific.
At the end of the second day I also somehow managed to damage my knee in some way (I'm not sure how) which made it much more uncomfortable to walk. And as we settled down at our campsite for our second night we met some other groups from a different school, and when we asked them how far they had to walk we were outraged. They only had to walk 15 kilometres! This is because the actual requirement for the Silver Award is about six hours of walking per day – there is no set distance! This really aggravated our entire group because we had to suffer an extra eight kilometres every day because our school are really pushy. However not all was bad: the other school gave us lots of their food because they 'felt sorry for us'.
However the two injuries to my legs, along with my blisters, were not my only problems. By the end of the second day I had tremendously painful chafing on the inside of my legs. This made any sort of walking impossible, and I ended up being laughed at by everybody I passed because I was forced to waddle like a penguin, with my legs wide apart. Therefore I decided to retire early, and lay in my tent while my group watched the football.
The final day was absolute hell. I spent almost all the day stumbling along behind my group while they shouted 'Hurry up!' over and over. At many points I thought, and so did they, that I would not make it. I contemplated ringing the teacher and telling him that I could walk no further, for fear of permanently damaging either my feet or my legs. Nonetheless I reached the end just as it began to pour with rain, and to my great pleasure, was provided with a box of fish and chips. We still had to wait a couple of hours for one of the groups who had gotten terribly lost, and had taken an hour or so detour.
I find it rather ironic how three of my life's most unpleasant experiences (Hematoma, sleeping in a blizzard and chafing/blisters) all took place on my Silver D of E expeditions, and yet I still very much enjoyed them. And although the walking was somewhat traumatic I still relished the experience and look forward to Gold! And despite losing a few days of my holiday, I'm glad I have now completed the Award. However, a month on, my blisters have yet to heal, and I was unable to walk for about a week after the expedition.


text:
Most new buildings or major changes to existing buildings or to the local environment need consent - known as planning permission. Without a planning system everyone could construct buildings or use land in any way they wanted, no matter what effect this would have on other people who live and work in their area.
Your local planning authority is responsible for deciding whether a development - anything from an extension on a house to a new shopping centre - should go ahead. Find your local planning authority.
You can apply for planning permission and a range of other consents online through the Planning Portal.
Start an online planning application
This section provides an overview of the planning system in England, including information about planning permission and how you can get involved in local decision making.
Find out more about the legal framework which underpins the planning system in England, including key Acts of Parliament, Government Circulars, Planning Policy, Guidance and links to live consultations.
Find out about statutory consultees in the planning process, and more detailed information about the common service commitment, roles, advice and contact details of English Heritage,
the Environment Agency,
the Health & Safety Executive, the Highways Agency and Natural England.
Learn more about installing renewable energy systems in your home such as solar panels, wind turbines and biomass heaters. You can also find out about energy-saving measures such as cavity wall insulation, glazing and heating.
Learn more about the process for making an appeal against a planning decision or non-determination of an application, search for an existing appeal and make a comment on it, or submit an appeal online.
Practical guides to specialist areas of the planning system, e.g. mobile phone masts and sports clubs, etc
Access a range of useful advice and tools for submitting online planning applications via the Portal.
The Planning Portal works with local authorities to deliver key efficiencies within the planning process, such as the introduction of the online application service. Find out other ways the Portal can help LPAs.


text:
Well.. I slept all the day and now still i feel sleepy. This has been going from last 1 month. Usually, i don't sleep much when i have to go out or work somewhere. But, whenever there is something important coming up in the near future, like an exam or an interview, my brain automatically forces me to sleep.
And yeah.. mind you.. this is not the 8 hour sleep that we usually do. But this is 18 hour sleep a day. Given a chance, i will sleep even 24 hrs a day comfortably. I don't know why, but i developed this disorder right from my school days. An exam is coming up, i am gearing up for sleep.. an interview is coming up, i am getting ready to sleep..
Any number of teas or cigarettes don't work for me. They don't keep me awake. I don't know the reason why. Any disorder this is ?? OMG.. i ve had enough.. i don't want to add one more to this list. I have an important exam coming up in the next 8 days and now i am sleeping 8 hours completely -- 2 times a day.. i.e. a total of 16 hours a day. When the exam is done, i will not be able to sleep even if i want to. This has been happening from so long and i think some one should suggest me to do something to stop it. because i ve tried everything and tired by now.
Good night.. :(


text:
By completing your order, you understand that the products(s) you are purchasing are U.S. models and may have power / voltage requirements different from that of your country.
Prices shown in currencies other than US Dollars are estimates based on current exchange rates. We will charge your credit card in US Dollars on the day your order is shipped, and the conversion to your local currency will be done at the prevailing rate by your credit card issuer.
ProSound and Stage Lighting will not mark your parcel as a "gift", declare a value lower than the actual price paid, or otherwise prepare false customs information.
This handy party-goer is equipped with the "Double Bubble Wheel" designed to produce a solid, plentiful amount of bubbles continuously. The W-101´s reservoir holds 1-liter of bubble liquid that will keep making bubbles for up to 2 hours continuously. Just plug in, fill up and the unit instantly produces bubbles.
Easy refills and the included hanging bracket makes the W-101 very user-friendly. The innovative smart-intelligence lies with the learning-mode of the wireless function. Where each receiver can memorize up to 5 sets of frequencies and all receivers can receive signals from any registered transmitter.
One wireless controller comes standard.Features:
*Wireless range is up to 50M (meters)
**Wireless distance may vary depending on the interference


text:
'Davy Crockett' Actor Fess Parker Dies At 85
View Single Post
Skunk Works
SpursReport Team Bench
Join Date: Dec 2008
Posts: 1,124
R.I.P. Actor Fess Parker Dies At 85
'Davy Crockett' Actor Fess Parker Dies At 85
Family Says Actor Died From Natural Causes
POSTED: Thursday, March 18, 2010
UPDATED: 3:02 pm CDT March 18,2010
"Davy Crockett" and "Daniel Boone" star-turned-developer and vintner Fess Parker has died. He was 85.
Family spokeswoman Sao Anash said Parker died at 10 a.m. Thursday of natural causes at his Santa Ynez home near the Fess Parker Winery. His death comes on the 84th birthday of his wife of 50 years, Marcella.
Parker became every baby boomer's idol in the 1950s when he starred as frontiersman Davy Crockett.
Kids grabbed up Davy Crockett lunch boxes, toy Old Betsy rifles, buckskin shirts and trademark fur caps. The series theme song - "The Ballad of Davy Crockett" - became a hit with its line "Born on a mountaintop in Tennessee."
Parker played Daniel Boone in the late 60s television show.
He later became a developer along California's Central Coast and grew grapes for prize-winning wines.
'Davy Crockett' Actor Fess Parker Dies At 85 - Entertainment News Story - KSAT San Antonio
"When Events Test Men, Angels Appear"
Skunk Works
View Public Profile
Find all posts by Skunk Works


text:
Sorry, no definitions found. Check out and contribute to the discussion of this word!
Sorry, no etymologies found.
Astronomers have found a super-earth exoplanet 37 light years away from our solar system Photograph: Anonymous/AP
Despite the fact that we theoretically have the capabilities to detect earth sized planets in their Goldie-locks zones we have thus at best been able to verify only down to the super-earth size.
If the Earth is Rare, We May Not Hear from ET | Universe Today
Based on the recent discovery of a super-earth around a red dwarf star 9,000 light-years away, the research team calculated that there are probably 3 times as many of these planets than the larger gas giants.
However, on a "super-earth" planet that's a name I don't like, they only mean 'larger than earth' the gravity would be much greater.
It is in the constellation of Vela and classed as a "super-earth" as it is much larger than our planet - around 3.6 times the Earth's mass - and is constantly the right distance from its main star to be neither too cold nor too hot.
Telegraph.co.uk - Telegraph online, Daily Telegraph and Sunday Telegraph
Gliese 581-d is a super-earth about a red dwarf star, likely habitable, but it will require a greenhouse effect or internal heat generation to make it be so, and it requires a substantially thick atmosphere currently unknown to even make liquid water exist.
WFIRST, and ramp up Cosmic Visions for a super-earth detector and be going before NASA gets to any sort of TPF concept.
They define a "water planet" as any super-earth whose mass is more than 10% water, whose core is made of silicates or metals, and whose surface layer is lacking in significant amounts of gas.
"Since we found the super-earth using a small ground-based telescope, this means that anyone else with a similar telescope and a good CCD camera can detect it too.
Students around the world can now study this super-earth! "said David Charbonneau of CfA, lead author and head of the MEarth project.


text:
RxActions. RxJava static helper methods for combining multiple actions into single action stream.
This is Open Source project.
RecyclerView provides adapter that provides a binding from an app-specific data set to views. In a case of different type of data set, adapter requires to specify unique view type per each data set. This will lead to checking view type using switch/ifelse as well as implementing multiple ViewHolders in the single adapter.
This library's purpose to solve the described issue above by splitting responsibility of the adapter to create and bind each item view type separately.
This is Open Source project.
I'm proud to introduce you XWindows Dock. It makes your work much easier on your PC.
By the way, since XWindows Dock 2.0 beta has been introduced back in January, 2010, it was downloaded more than 670 850 times, and 1 770 000 people visited official website!
This is Open Source project.
One of the most common questions in Android dev world is: How to communicate between Activity and Service. Problem here is that starting service is simple, but returning result can be a challenge. Most common solutions are ResultReceiver, Messenger, BroadcastReceiver (LocalBroadcastManager) and others. They all will work just fine, but they all are IPC/RPC, they all are used to communicate across different applications. What to do in a case of single app?
This is Open Source project.
You'r Android developer. You like Functional Programming and tired of only imperative Java way.
This is for you - Kotlin is new language that is good enough for Dalvik VM, compiles same Java byte code and keep same speed.
This is Kotlin Android Library and it's Open Source project.
Do you need simply transfer some files from your PC to another one too often? That's a solution.
AirFileExchange gives you opportunity to exchange files between PCs in local network by 2 clicks.
This is Open Source project and Just for Fun. Watch a video. Download
When you need to write UI for Android by hands, you need know XML and type a lot. If you are familiar with Lisp, you know (name value) expression is cool and easy. Let's use this idea.
"<name attr1="value1"><child attr2="value2" /></name>" will looks on Lisp-like: "(name (attr1 value1) (child (attr2 value2)))"
Not cool? Just copy AndroidXMLayouter_x.x.x.jar to Eclipse plugin directory, restart Eclipse, open .xml file, type Lisp-like code, right click "Generate Android XML", done.
This is Open Source project. Watch a video. Download
Simple tool should run before Java compiler to translate some structures of the language to 'clean' Java code.
All arguments passes to this tool has to be *.fjava files, that can even have no FJava structures. Tool will create .java file with same name in same package (folder) so newly created java file can be compiled by Java compiler.
Be able to use this tool it's required to add com.fjava.library to classpath to your project. There are no files to be attached to your code, except if you use, for example, () => {} structure, tool will replace it with some interface F<...>(...) so this file will be compiled by Java compiler and attached to your project. If you don't use any structured, additional files won't be attached at all.
This is Open Source project.


text: c++, Featured, Members, Objects, Other Published: 24/05/2012 | Views: 5,967 | comments 3 'Signal to Noise' by LAb[au] – 512 mechanical split-flaps and the noise of data written by Filip Visnjic Sorry, this is Members Only content. Please Log-in. To find out how to become a member see here. Tweet


text:
Tuesday, July 15, 2014
"You're the Best" - Fresh Brewed Designs - In the sky challenge
5 comments:
- Julie Tucker-Wolek said...
This is sooooooo fun! LOVING that image!!!!!
- Tuesday, 15 July, 2014
- Heather D. ~ Fresh Brewed Designs said...
HEHEHE!!! Look at Granny! This is AWESOME! Love the sand and sea in the background. The twine is perfect and Granny looks as lovely as can be! Adorable sky!
Thank you so much for playing along with us at Fresh Brewed Designs in the sky challenge.
Heather D.
- Tuesday, 15 July, 2014
- Taunya Butler said...
Awesomely done card!! Love the image, the sunshine, the twine at the bottom with a button - just all comes together to make this card fantastic!!!
- Tuesday, 15 July, 2014
- Beth Brovold said...
What a wonderful post Michele!! I too would love to be joining Granny on your wonderful beach...she does look so calm and relaxed!! Thanks for sharing your creativity with us at Fresh Brewed Designs!!
Take care,
Beth FB DT
- Thursday, 17 July, 2014
- Elizabeth Campau said...
Oh what a fun card Michele. It made me smile:)
- Saturday, 19 July, 2014


text:
Today, I visited Shara in her home and was able to see some of her paintings. I've always known that she was a great artist/painter, but OH MY GOSH!, she's brilliant...truly! These pictures are just a couple glimpses of her talent, but if you'd like to see more of her work, go to Studio Shara and you'll find pieces that will make you smile...from illustrations to family portraits, her work is without question...AMAZING!
|photo credit: Studio Shara
|photo credit: Studio Shara
I'd like the world to know the name, SHARA BRAITHWAITE and I'll simply start by introducing her to some of you on my tiny little blog.


text:
About this item
- One package of 6 corn dogs
- Classic hot dog on a stick dipped in honey-sweetened batter
- Made with real chicken, turkey, pork, and beef and no added hormones or steroids
- 6 grams of protein per serving
- Fun and tasty way to help give your kids the fuel they need for their play
- Simply microwave and serve
Give your kid this State Fair favorite: a super-yummy, batter-wrapped hot dog on a stick. State Fair Classic Corn Dogs are made with real chicken, turkey, pork, and beef with no added hormones or steroids, then dipped in honey-sweetened batter for a kid-approved snack that moms will love as well. With 6 grams of protein per serving, our Classic Corn Dogs are a tasty way to give your kids the protein they need to help power their play. Simply microwave and serve with fruits and veggies for a delicious and well-balanced snack. Includes one package of 6 fully cooked corn dogs. Did someone say playtime? We're ready. From the secret superhero fort in the backyard to the stuffed animal zoo in your basement, play is the most important thing in a kid's world. With State Fair Corn Dogs, your kids get a good source of protein to keep the fun going. So line up the play dates, bring on the playgrounds, and play on.
Contains: Wheat, soy, Milk, eggs
May Contain: Eggs
Serving Size: 1.0 pieces
Good Source Of: Protein
Store: In a Frozen location at Frozen
Exterior Container: Paper or cardboard Box
Main Ingredient: Meat
State of Readiness: Prepared, heat and serve
Servings: 6.0, Approximate
Pre-package preparation: Fully cooked
Package type: Individual item multi-serving
Exterior container weight: 16.0 ounces
Item Number (DPCI): 210-02-0134
Grocery Disclaimer:
Content on this site is for reference purposes only. Target does not represent or warrant that the nutrition, ingredient, allergen and other product information on our Web or Mobile sites are accurate or complete, since this information comes from the product manufacturers. On occasion, manufacturers may improve or change their product formulas and update their labels. We recommend that you do not rely solely on the information presented on our Web or Mobile sites and that you review the product's label or contact the manufacturer directly if you have specific product concerns or questions. If you have specific healthcare concerns or questions about the products displayed, please contact your licensed healthcare professional for advice or answers. Any additional pictures are suggested servings only.
If the item details above aren't accurate or complete, we want to know about it. Report incorrect product info.
see store for price
not available
Ratings & reviews
Prices, promotions, styles and availability may vary by store & online. See our price match guarantee. See how a store is chosen for you.


text:
Cosplay Cutie Molested
Her soft and tender breast is thoroughly rubbed while her pussy is soaking wet after being fingered real hard.
Asian Beauty
Her Body Is Yours
She has taken off her undies, half naked lying on the floor waiting for you. Her thick black hairy pussy is simply irresistible. She wants you to fondle her whole body now.
Can You Satisfy Her?
Naked Singaporean Girlfriend
Sweet Young Girl Molested
Cute girl molested by 2 horny guys.
I'm losing control, feels so good...
Ohh......play with my pussy...
I'm reaching orgasm!
Hairy Pussy
Naked Cosplay Girl
Subscribe to: Posts (Atom)


text:
This upcoming weekend WBA welterweight champion Keith "One Time" Thurman (25-0, 21 KO's) will be returning to the ring for the second time in five months as he takes on Luis Collazo (36-6, 19 KO's) in his hometown of Tampa Bay, FL. The fight will be televised on ESPN as part of the PBC series.
For Keith Thurman, the road to stardom is a tougher one than most despite being in a weight class of big names. Thurman is considered by many as a knockout artist that brings excitement every time he steps into the ring, however, he has yet to break into that stardom limelight. He's been having a hard time getting the big names to step into the ring with him. Patience is a virtue, and Thurman is trusting that advisor Al Haymon is going to get him where he needs to be.
"It's a business and it takes time. I've been on the scene for three years now and just earlier this year I got my first fighter in the top ten and to a degree it's a struggle man but it's a grind and I look forward to the grind." Thurman stated.
Thurman is considered the most dangerous fighter in the welterweight division tallying up a knockout percentage of %81 in 25 professional fights. Robert Guerrero was willing to step up to the plate in March and Thurman hopes that more fighters will follow his path. For now Thurman is just trusting the plan and he knows that his knockouts are helping him land the PBC Main Events. This will be the second time that Thurman will headline a PBC card in five months which means millions of viewers with their eyes on him again.
"I'm somewhat of a go to guy. I'm reliable you can trust me. I show up I make weight. I stay true to the contract. There hasn't been a lot of controversy with me and my career. Our team is dedicated and I just believe that Al sees that and he's taking advantage of my hunger and just trying to grow me as a fighter."
Thurman plans to fight four times a year under the PBC. With fighters like Floyd Mayweather, Manny Pacquiao, Shawn Porter, Kell Brook, Amir Khan, Timothy Bradley, Marcos Maidana, and many more stacking up the welterweight division the options for Keith Thurman seem to be endless.
Knockouts sell in boxing. It's not a matter of opinion but a fact. Thurman brings that every time he steps into the ring. With explosiveness in his punches, and knockout power behind each time he throws, the road to stardom shouldn't be hard. Besides his in the ring excitement, outside of the ring Thurman is fun, witty, and enjoys much of what boxing has brought him. Last week he spent some time at Shriner's Hospital of Children in his hometown of Tampa Bay sharing his story with the children there. With a personality that includes amusing 4th of July video's and him playing the flute on Twitter, Thurman has the makings of everything it takes to help be the face of boxing once Floyd Mayweather and Manny Pacquiao have retire. He also had some choice words for Floyd Mayweather, who claimed that Thurman wasn't ready for him.
"He fought Victor Ortiz was he ready? He fought Robert Guerrero was he ready? C'mon." Thurman told the Boxingvoice.
For now, he claims his focus is on Luis Collazo on July 11th.Thurman understand that a trap fight can ruin everything. While he itches for the bigger names in his division like Floyd Mayweather he understands how the sport of boxing works and will not look past any fight.
"At the end of the day, my job is to win. Everything else is icing on the cake. We want to be great. We want this match to be talked about for months to come later on in the year. We stayed focused to the formulas. It's another fight, it's another opportunity for me to showcase my skills and my talents to the world and I don't believe that I've disappointed anybody yet. July 11 shouldn't be any different."


text:
JustDrive +
JustDrive+ - The intelligent benefit solution
Inchcape Fleet Solutions JustDrive+ is a new, ground-breaking product development to provide IFS customers with an innovative way to help attract, recruit and retain loyal employees by improving their employee benefits package.
This innovative car salary sacrifice scheme is an enhancement of the established IFS Justdrive scheme with integration of the advanced functionality of Autobid, IFS's award-winning competitive tendering product
Inchcape Fleet Solutions JustDrive+, allows your employees to trade an element of their salary in exchange for a brand new car, with all of the usual benefits associated with a company vehicle.
The IFS JustDrive+ product is beneficial due to the cost of the car being deducted from the employee's gross salary, resulting in Tax and National Insurance (NI) savings.
This new, ground-breaking product integrates IFS Autobid functionality to provide your employees with competitive, real-time quotes from a panel of market-leading funders for the cars they order through the Justdrive system. Taking advantage of market forces, this innovative system sources the best quote available and delivers best value pricing directly back to IFS customers.
You can then choose to share the resulting cost savings with your employees; thus further enhancing your employee benefits package.
IFS customers also benefit from our enhanced corporate buying power and manufacturer discount terms. These savings can also then be passed on to your employees, providing them access to a fully maintained vehicle of their choice at a fraction of the price they would achieve in the open market.
JustDrive+ can be tailored to your exact business requirements and the user-friendly online portal enables employees to order their cars directly online, creating minimal administration for employers.
The car salary sacrifice concept is fully HMRC compliant and IFS JustDrive+ supports your company's duty of care obligations as your employees are driving newer, safer cars.
With no credit check required, fully comprehensive private & business insurance included and all of their servicing, breakdown and accident management taken care of through IFS's industry leading fleet management service, your employees are able to just add fuel and drive a brand new, cost efficient car.


text:
You may or may not have noticed that residential water rates have inched upward. To conserve water and save on your water bill, SAWS customers can apply through October 31, 2017, for coupons worth up to $800 to help replace lawn grass with drought-tolerant garden beds and/or permeable patios. For details, check the SAWS newsletter that comes with your water bill or go to www.gardenstylesanantonio.com/coupons-and-rebates.
Current SAWS requirements allow for landscape watering any day of the week before 11:00 a.m. and after 7:00 p.m. Watering early in the day will reduce various diseases that can infect lawns and plants. As it gets warmer and dryer, restrictions can change.
Fall through late winter is the best time to plant trees; however, there are instances when planting at other times may be needed as with blooming trees such as crepe myrtles. They are beginning to bloom now, and if a particular color is desired to complement a garden color scheme, this is the time to make your selection. They will need to be watered more frequently over the summer and fall to prevent roots from drying out. Use an organic liquid fertilizer at half strength about every third time you water.
Do you have a small garden, no garden, or just do not like "to play in the dirt," but enjoy seeing beautiful nature scenes? Take a trip to the San Antonio Botanical Garden. In spring and early summer plants are at their peak. The Garden is truly a San Antonio treasure. Details are at sabot.org.
From The Wit and Wisdom of Mark Twain: A Book of Quotations: Do not put off till tomorrow what can be put off till day-after-tomorrow just as well.
Garden Note: Those who plant a garden, plant happiness.


text:
Rural Medical Education Center
Kudat was selected as proposed by first Vice-Chancellor of UMS, Yang Berbahagia Tan Sri Profesor Datuk Seri Panglima Dr. Abu Hassan Othman as a place for family activities in rural area in March 2004.
Rural Medical Education Center (RMEC) was built in Sikuati area and located about 180 km from main campus of Universiti Malaysia Sabah which was inaugurated by the Minister of Higher Education Malaysia, YB Dato Seri Mohamed Khaled Nordin on 18 January 2009. Previously it was operated at shop lot in Sikuati town.
This centre has an area of 20 acres / 8.09371 hectare and made up of several building blocks which are equipped with facilities as needed especially for year 4 medical students and for staffs.
Building blocks are consist with:
1. Administration
2. Academic
3. Multipurpose Hall
4. Clinic and Research
5. Hostel
6. Staff House Apartment
7. Lecturers House


text:
Check out one of the coolest episodes of Sneaker Shopping yet.
Chris Rock recently paid a visit to Stadium Goods in NYC with Complex's Joe La Puma to talk about all things sneaker-related including why the Yeezys are a must-have, the history of Nike's "Lil Penny" character, and the importance of having a "What the hell is that" pair of sneakers.
Also in this episode, Chris Rock spoke about what it was like working with Michael Jordan when he hosted SNL back in 1991. At the end of his trip to Stadium Goods he walked out with four pairs of kicks totalling nearly $2,400.
Check out the latest episode of Sneaker Shopping below.


text:
(Redirected from Show Time)Jump to navigation Jump to search
|Look up showtime in Wiktionary, the free dictionary.
Showtime or Show Time may refer to:
Film and television[edit]
- Showtime Networks, a division of CBS which owns the Showtime brand
- Showtime (TV network), a cable and satellite TV network headquartered in the U.S., part of the CBS division called "Showtime Networks"
- Showtime Arabia, former dominant TV service in the Middle East and North Africa, has since been merged into a pay-TV network called "OSN"
- Showtime Movie Channels, a suite of Australian premium networks owned under a studio consortium which licenses the Showtime name
- Showtime Scandinavia, a television channel broadcasting action movies to the Nordic countries
- Showtime (film), a 2002 American action/comedy film
- Showtime (Australian TV series), a 1959–1960 Australian variety television series
- Showtime (Croatian TV series), a 2007 Croatian talent show similar to Pop Idol
- Showtime (South Korean TV series), a South Korean reality television series that has aired on MBC Every 1 since 2013
- Showtime (Philippine TV series), now known as It's Showtime (TV program), a Philippine noontime variety show
- Showtime at the Apollo, a syndicated music program
- "Showtime" (Buffy the Vampire Slayer), an episode of Buffy the Vampire Slayer
- "Showtime" (M*A*S*H), an episode of M*A*S*H
- "Showtime", an episode of Law and Order
- Showtime!, an album by The J. Geils Band
- Showtime (Angel & Khriz album)
- Show Time (Arnett Cobb album)
- Showtime (Avril Lavigne album)
- Showtime (Bro'Sis album)
- Showtime (Dizzee Rascal album)
- Showtime (James Brown album)
- Showtime (Mick Ronson album)
- Showtime (Nitzer Ebb album)
- Showtime (video), a live concert video by Blur
- Show Time (Doris Day album)
- Show Time (Show Lo album)
- Showtime, an album by TV-2
- Showtime, an album by Ry Cooder
- Showtime: Still 51/50, an upcoming album by Hurricane Chris
- "Show Time", a 1967 song by The Detroit Emeralds
- "Showtime", a song by Lil Wayne from Tha Carter III
- "Showtime", a song by Nelly Furtado from Loose
- "Showtime", a song by Lower Than Atlantis from Changing Tune
- "Showtime", a song by MC Ren from Renincarnated
- Showtime (basketball), a style of basketball associated with the Los Angeles Lakers from 1979 to 1991
- Showtime (busking), a dance style for buskers in the New York City Subway
- Showtime All-Star Wrestling, an American professional wrestling promotion based in Nashville, Tennessee
Sportspersons with the nickname[edit]
- Eric Young (wrestler) (born 1979), Canadian professional wrestler
- Zakeem Graham (born 1970), American boxer
Other uses[edit]
- Showtime, a fragrance endorsed by Kylie Minogue
- Showtime Rotisserie, a small oven invented and advertised by Ron Popeil
- The Sims 3: Showtime, the sixth expansion pack for The Sims 3
- "Showtime" Marching Band, a marching band from Howard University in Washington, DC
See also[edit]
- All pages with a title containing Showtime
- All pages with a title containing show time
- It's Showtime (disambiguation)
- show (disambiguation)
| disambiguation page lists articles associated with the title Showtime.
If an internal link led you here, you may wish to change the link to point directly to the intended article.