[openstack-dev] [nova] Newton Instance Snapshot Capability Extended
Hi All, I have proposed a blueprint (https://blueprints.launchpad.net/nova/+spec/instance-memory-snapshot) and nova spec (https://review.openstack.org/#/c/295415/) to improve the current snapshot capability. In the past this topic has been introduced and several times it has been left behind. Is there any interest in this topic in any capacity or is there a reason why this hasn't been extended before? __ OpenStack Development Mailing List (not for usage questions) Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
[openstack-dev] [nova] Instance Snapshot Capability Extended
Hi All, I have proposed a blueprint (https://blueprints.launchpad.net/nova/+spec/instance-memory-snapshot) and nova spec (https://review.openstack.org/#/c/295415/) to improve the current snapshot capability. In the past this topic has been introduced and several times it has been left behind. Is there any interest in this topic in any capacity or is there a reason why this hasn't been extended before? __ OpenStack Development Mailing List (not for usage questions) Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
Re: [openstack-dev] [Heat] Introducing Re-Heat
> > > > > > Hello All, > > > > > > > > My name is Mika Ayenson and I have to privilege to intern at Johns > > Hopkins - Applied Physics Lab. I’m really excited to release the > > latest proof of concept “Re-Heat” Re-Heat is a JHUAPL developed tool > > for OpenStack users to help them quickly rebuild their OpenStack > > environments via OpenStack’s Heat . > > > > > > > > Here is a link to the Re-Heat paper: > > https://drive.google.com/open?id=0BzTq-ZB9F-b9b0ZXdy1PT2t3dk0&authuser > > =0 > > > > Here is a link to Re-Heat: https://github.com/Mikaayenson/ReHeat > > Hi Mika, > > It looks very similar to the flame project I've been contributing recently: > > https://github.com/cloudwatt/flame > > It's be interesting to see if we can join forces. > > Cheers, > > -- > >Thomas > > ___ > > OpenStack-dev mailing list > > OpenStack-dev@lists.openstack.org > > http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev Hello Thomas, I have seen flame! I think that it's a great project. I believe you are right. I believe there are ideas in both projects that should be merged. I'm hoping that eventually users will be able to snapshot environments as a stack template. Later even have a template management system so that users may be able to revert their environment back to an original stack template. This will be great for testing purposes. If you take a look at the paper, we briefly mentioned Flame as well! I'm hoping that people will be able to see the use cases and power of tools like these. ___ OpenStack-dev mailing list OpenStack-dev@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
[openstack-dev] [Heat] Introducing Re-Heat
Hello All, My name is Mika Ayenson and I have to privilege to intern at Johns Hopkins - Applied Physics Lab. I'm really excited to release the latest proof of concept "Re-Heat" Re-Heat is a JHUAPL developed tool for OpenStack users to help them quickly rebuild their OpenStack environments via OpenStack's Heat . Here is a link to the Re-Heat paper: https://drive.google.com/open?id=0BzTq-ZB9F-b9b0ZXdy1PT2t3dk0&authuser=0 Here is a link to Re-Heat: https://github.com/Mikaayenson/ReHeat I have included the abstract to our paper here: Abstract OpenStack has experienced tremendous growth since its initial release just over four years ago. Many of the enhancements, such as the Horizon interface and Heat, facilitate making complex network environment deployments in the cloud from scratch easier. The Johns Hopkins University Applied Physics Lab (JHU/APL) has been using the OpenStack environment to conduct research, host proofs-of-concepts, and perform testing & experimentation. Our experience reveals that during the environment development lifecycle users and network architects are constantly changing the environments (stacks) they originally deployed. Once development has reached a point at which experimentation and testing is prudent, scientific methodology requires recursive testing be conducted to determine the repetitiveness of the phenomena observed. This requires the same entry point (an identical environment) into the testing cycle. Thus, it was necessary to capture all the changes made to the initial environment during the development phase and modify the original Heat template. However, OpenStack has not had a tool to help automate this process. In response, JHU/APL developed a poof-of-concept automation tool called "Re-Heat," which this paper describes in detail. I hope you all enjoy this as I have truly enjoyed playing with HEAT and developing Re-Heat. Cheers, Mika Ayenson ___ OpenStack-dev mailing list OpenStack-dev@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
