Re: [openstack-dev] OVF/OVA support
HI Dmitry, I was not able to attend, by Alex was on this session. I will check what was discussed. Even if it was not discussed on the summit, we can continue to discuss it here in the mailing list. Thanks Gosha On Tue, Nov 11, 2014 at 4:39 AM, Dimitri Mazmanov < dimitri.mazma...@ericsson.com> wrote: > Hello, > I’m also interested in having OVF package support for applications. > As it was described earlier, there are two main tracks to this – OVF > artefacts in Glance (corresponding driver), and translating OVF descriptors > to Heat templates. > Is there any etherpad from the session? > - > Dimitri > > From: , Malini K > Reply-To: "OpenStack Development Mailing List (not for usage questions)" < > openstack-dev@lists.openstack.org> > Date: Friday 7 November 2014 15:18 > To: Georgy Okrokvertskhov > Cc: OpenStack Development Mailing List > Subject: Re: [openstack-dev] OVF/OVA support > > Gosha – this is wonderful news. Complements Intel interest. > > I am in the Glance area .. stopped by a couple of times, the room was > available 2 pm onwards. > > Contact made and can continue via email and IRC. > > Malini > > > > *From:* Georgy Okrokvertskhov [mailto:gokrokvertsk...@mirantis.com > ] > *Sent:* Friday, November 07, 2014 8:20 AM > *To:* Bhandaru, Malini K > *Cc:* OpenStack Development Mailing List > *Subject:* Re: OVF/OVA support > > > > Hi Malini, > > I am interested in OVa support for applications. Specifically Ova to Heat > as this is whay we usually do in Murano project. > > When is free format session for Glance? Should we add this to session > etherpad? > > Thanks, > Gosha > > On Nov 5, 2014 6:06 PM, "Bhandaru, Malini K" > wrote: > > Please join us on Friday in the Glance track – free format session, to > discuss supporting OVF/OVA in OpenStack. > > > > Poll: > > 1) How interested are you in this feature? 0 – 10 > > 2) Interested enough to help develop the feature? > > > > > > Artifacts are ready for use. > > > > We are considering defining an artifact for OVF/OVA. > > What should the scope of this work be? Who are our fellow travelers? > > Intel is interested in parsing OVF meta data associated with images – to > ensure that a VM image lands on the most appropriate hardware in the cloud > instance, to ensure optimal performance. > > The goal is to remove the need to manually specify image meta data, allow > the appliance provider to specify HW requirements, and in so doing reduce > human error. > > Are any partners interested in writing an OVF/OVA artifact => stack > deployment? Along the lines of heat? > > As a first pass, Intel we could at least > > 1) Defining artifact for OVA, parsing the OVF in it, pulling out the > images therein and storing them in the glance image database and attaching > meta data to the same. > > 2) Do not want to imply that OpenStack supports OVA/OVF -- need to > be clear on this. > > 3) An OpenStack user could create a heat template using the images > registered in step -1 > > 4) OVA to Heat – there may be a loss in translation! Should we > attempt this? > > 5) What should we do with multiple volume artifacts? > > 6) Are volumes read-only? Or on cloning, make copies of them? > -- Georgy Okrokvertskhov Architect, OpenStack Platform Products, Mirantis http://www.mirantis.com Tel. +1 650 963 9828 Mob. +1 650 996 3284 ___ OpenStack-dev mailing list OpenStack-dev@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
Re: [openstack-dev] OVF/OVA support
Hello, I’m also interested in having OVF package support for applications. As it was described earlier, there are two main tracks to this – OVF artefacts in Glance (corresponding driver), and translating OVF descriptors to Heat templates. Is there any etherpad from the session? - Dimitri From: , Malini K mailto:malini.k.bhand...@intel.com>> Reply-To: "OpenStack Development Mailing List (not for usage questions)" mailto:openstack-dev@lists.openstack.org>> Date: Friday 7 November 2014 15:18 To: Georgy Okrokvertskhov mailto:gokrokvertsk...@mirantis.com>> Cc: OpenStack Development Mailing List mailto:openstack-dev@lists.openstack.org>> Subject: Re: [openstack-dev] OVF/OVA support Gosha – this is wonderful news. Complements Intel interest. I am in the Glance area .. stopped by a couple of times, the room was available 2 pm onwards. Contact made and can continue via email and IRC. Malini From: Georgy Okrokvertskhov [mailto:gokrokvertsk...@mirantis.com] Sent: Friday, November 07, 2014 8:20 AM To: Bhandaru, Malini K Cc: OpenStack Development Mailing List Subject: Re: OVF/OVA support Hi Malini, I am interested in OVa support for applications. Specifically Ova to Heat as this is whay we usually do in Murano project. When is free format session for Glance? Should we add this to session etherpad? Thanks, Gosha On Nov 5, 2014 6:06 PM, "Bhandaru, Malini K" mailto:malini.k.bhand...@intel.com>> wrote: Please join us on Friday in the Glance track – free format session, to discuss supporting OVF/OVA in OpenStack. Poll: 1) How interested are you in this feature? 0 – 10 2) Interested enough to help develop the feature? Artifacts are ready for use. We are considering defining an artifact for OVF/OVA. What should the scope of this work be? Who are our fellow travelers? Intel is interested in parsing OVF meta data associated with images – to ensure that a VM image lands on the most appropriate hardware in the cloud instance, to ensure optimal performance. The goal is to remove the need to manually specify image meta data, allow the appliance provider to specify HW requirements, and in so doing reduce human error. Are any partners interested in writing an OVF/OVA artifact => stack deployment? Along the lines of heat? As a first pass, Intel we could at least 1) Defining artifact for OVA, parsing the OVF in it, pulling out the images therein and storing them in the glance image database and attaching meta data to the same. 2) Do not want to imply that OpenStack supports OVA/OVF -- need to be clear on this. 3) An OpenStack user could create a heat template using the images registered in step -1 4) OVA to Heat – there may be a loss in translation! Should we attempt this? 5) What should we do with multiple volume artifacts? 6) Are volumes read-only? Or on cloning, make copies of them? ___ OpenStack-dev mailing list OpenStack-dev@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
Re: [openstack-dev] OVF/OVA support
Gosha – this is wonderful news. Complements Intel interest. I am in the Glance area .. stopped by a couple of times, the room was available 2 pm onwards. Contact made and can continue via email and IRC. Malini From: Georgy Okrokvertskhov [mailto:gokrokvertsk...@mirantis.com] Sent: Friday, November 07, 2014 8:20 AM To: Bhandaru, Malini K Cc: OpenStack Development Mailing List Subject: Re: OVF/OVA support Hi Malini, I am interested in OVa support for applications. Specifically Ova to Heat as this is whay we usually do in Murano project. When is free format session for Glance? Should we add this to session etherpad? Thanks, Gosha On Nov 5, 2014 6:06 PM, "Bhandaru, Malini K" mailto:malini.k.bhand...@intel.com>> wrote: Please join us on Friday in the Glance track – free format session, to discuss supporting OVF/OVA in OpenStack. Poll: 1) How interested are you in this feature? 0 – 10 2) Interested enough to help develop the feature? Artifacts are ready for use. We are considering defining an artifact for OVF/OVA. What should the scope of this work be? Who are our fellow travelers? Intel is interested in parsing OVF meta data associated with images – to ensure that a VM image lands on the most appropriate hardware in the cloud instance, to ensure optimal performance. The goal is to remove the need to manually specify image meta data, allow the appliance provider to specify HW requirements, and in so doing reduce human error. Are any partners interested in writing an OVF/OVA artifact => stack deployment? Along the lines of heat? As a first pass, Intel we could at least 1) Defining artifact for OVA, parsing the OVF in it, pulling out the images therein and storing them in the glance image database and attaching meta data to the same. 2) Do not want to imply that OpenStack supports OVA/OVF -- need to be clear on this. 3) An OpenStack user could create a heat template using the images registered in step -1 4) OVA to Heat – there may be a loss in translation! Should we attempt this? 5) What should we do with multiple volume artifacts? 6) Are volumes read-only? Or on cloning, make copies of them? ___ OpenStack-dev mailing list OpenStack-dev@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
Re: [openstack-dev] OVF/OVA support
Hi Malini, I am interested in OVa support for applications. Specifically Ova to Heat as this is whay we usually do in Murano project. When is free format session for Glance? Should we add this to session etherpad? Thanks, Gosha On Nov 5, 2014 6:06 PM, "Bhandaru, Malini K" wrote: > Please join us on Friday in the Glance track – free format session, to > discuss supporting OVF/OVA in OpenStack. > > > > Poll: > > 1) How interested are you in this feature? 0 – 10 > > 2) Interested enough to help develop the feature? > > > > > > Artifacts are ready for use. > > > > We are considering defining an artifact for OVF/OVA. > > What should the scope of this work be? Who are our fellow travelers? > > Intel is interested in parsing OVF meta data associated with images – to > ensure that a VM image lands on the most appropriate hardware in the cloud > instance, to ensure optimal performance. > > The goal is to remove the need to manually specify image meta data, allow > the appliance provider to specify HW requirements, and in so doing reduce > human error. > > Are any partners interested in writing an OVF/OVA artifact => stack > deployment? Along the lines of heat? > > As a first pass, Intel we could at least > > 1) Defining artifact for OVA, parsing the OVF in it, pulling out the > images therein and storing them in the glance image database and attaching > meta data to the same. > > 2) Do not want to imply that OpenStack supports OVA/OVF -- need to > be clear on this. > > 3) An OpenStack user could create a heat template using the images > registered in step -1 > > 4) OVA to Heat – there may be a loss in translation! Should we > attempt this? > > 5) What should we do with multiple volume artifacts? > > 6) Are volumes read-only? Or on cloning, make copies of them? > ___ OpenStack-dev mailing list OpenStack-dev@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
Re: [openstack-dev] OVF/OVA support
Malini, fyi, Vui/Arnaud is leading the charge in the Nova VMware driver with this review [1]. There is a spec in Nova also for multiple disks (for a single vm) from Tesshu [2]. thanks, dims [1] https://review.openstack.org/#/c/82715/ [2] https://review.openstack.org/#/c/128691/ On Thu, Nov 6, 2014 at 3:06 AM, Bhandaru, Malini K wrote: > Please join us on Friday in the Glance track – free format session, to > discuss supporting OVF/OVA in OpenStack. > > > > Poll: > > 1) How interested are you in this feature? 0 – 10 > > 2) Interested enough to help develop the feature? > > > > > > Artifacts are ready for use. > > > > We are considering defining an artifact for OVF/OVA. > > What should the scope of this work be? Who are our fellow travelers? > > Intel is interested in parsing OVF meta data associated with images – to > ensure that a VM image lands on the most appropriate hardware in the cloud > instance, to ensure optimal performance. > > The goal is to remove the need to manually specify image meta data, allow > the appliance provider to specify HW requirements, and in so doing reduce > human error. > > Are any partners interested in writing an OVF/OVA artifact => stack > deployment? Along the lines of heat? > > As a first pass, Intel we could at least > > 1) Defining artifact for OVA, parsing the OVF in it, pulling out the > images therein and storing them in the glance image database and attaching > meta data to the same. > > 2) Do not want to imply that OpenStack supports OVA/OVF -- need to be > clear on this. > > 3) An OpenStack user could create a heat template using the images > registered in step -1 > > 4) OVA to Heat – there may be a loss in translation! Should we attempt > this? > > 5) What should we do with multiple volume artifacts? > > 6) Are volumes read-only? Or on cloning, make copies of them? > > > ___ > OpenStack-dev mailing list > OpenStack-dev@lists.openstack.org > http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev > -- Davanum Srinivas :: https://twitter.com/dims ___ OpenStack-dev mailing list OpenStack-dev@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
[openstack-dev] OVF/OVA support
Please join us on Friday in the Glance track - free format session, to discuss supporting OVF/OVA in OpenStack. Poll: 1) How interested are you in this feature? 0 - 10 2) Interested enough to help develop the feature? Artifacts are ready for use. We are considering defining an artifact for OVF/OVA. What should the scope of this work be? Who are our fellow travelers? Intel is interested in parsing OVF meta data associated with images - to ensure that a VM image lands on the most appropriate hardware in the cloud instance, to ensure optimal performance. The goal is to remove the need to manually specify image meta data, allow the appliance provider to specify HW requirements, and in so doing reduce human error. Are any partners interested in writing an OVF/OVA artifact => stack deployment? Along the lines of heat? As a first pass, Intel we could at least 1) Defining artifact for OVA, parsing the OVF in it, pulling out the images therein and storing them in the glance image database and attaching meta data to the same. 2) Do not want to imply that OpenStack supports OVA/OVF -- need to be clear on this. 3) An OpenStack user could create a heat template using the images registered in step -1 4) OVA to Heat - there may be a loss in translation! Should we attempt this? 5) What should we do with multiple volume artifacts? 6) Are volumes read-only? Or on cloning, make copies of them? ___ OpenStack-dev mailing list OpenStack-dev@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
