jcvi-cloud/mi-deployment

Clone of Enis Afgan's mi-deployment (from bitbucket)

mi-deployment's Issues

Updating cm_boot.py (in ec2autorun.py:_get_boot_script) makes the file inaccessible

Somehow, the ACLs on the cm_boot.py file uploaded make it inaccessible.
Attempting to change or even read them results in a 401:permission denied error.
If I shut down cloudman and look at the database recreation script in /var/lib/eucalyptus/eucalyptus_walrus.script, the permission is set for full access for owner, and read-only for All Users, which should be OK. (e.g.
INSERT INTO GRANTS VALUES(1798,FALSE,TRUE,FALSE,FALSE,'http://acs.amazonaws.com/groups/global/AllUsers',NULL)
INSERT INTO GRANTS VALUES(1799,TRUE,TRUE,TRUE,TRUE,NULL,'rrichter')
)
However, the file is once again accessible if I remove the grant for AllUsers.
I'm not sure what's causing this.

Adapt mi_fabfile rebundle function for eucalyptus cloud

The primary issue here is that the image is being made here as a bootable EBS image (as it should be for AWS), which is not compatible with the current Eucalyptus.
It will need to be done instead by creating the image in a mounted volume, then uploading and registering it from there.

This is low priority, since I can manually create the image. In the long run, it should be automatable