Thanks Daniel and Marco.
I am using the qcow cloud images, but I'm also using newer versions of
OpenStack - Newton, Ocata, or the Pike master branch of OpenStack
installer projects.
I'll double check that Heat is correctly configured to use Glance and
keep plugging away until I can get the demo deployed.

Aimee Ukasick
Open Source Engagement OPFNV, OpenStack, ONAP

On 04/07/2017 03:26 PM, ROSE, DANIEL V wrote:
> Aimee,
> 
> 'does not validate glance.image' generally in my experience means heat cannot 
> find a type of that name (ie heat Is not correctly setup to use glance) not 
> that there is anything wrong with the image per se. I suspect you could 
> confirm this by using heat to spin up anything (like the cirros test image or 
> something). 
> 
> But to be more specific on the images, you need something like the 64 bit 
> cloud images (which are in qcow2 format if you use kvm) from 
> https://cloud-images.ubuntu.com/releases/14.04/release/ 
> and 
> https://cloud-images.ubuntu.com/releases/16.04/release/
> 
> 
> Thanks,
> Daniel Rose
> ECOMP / ONAP
> com.att.ecomp
> 732-420-7308
> 
> -----Original Message-----
> From: onap-discuss-bounces at lists.onap.org [mailto:onap-discuss-bounces at 
> lists.onap.org] On Behalf Of PLATANIA, MARCO
> Sent: Friday, April 07, 2017 3:15 PM
> To: Aimee Ukasick <aimeeu.opensource at gmail.com>; onap-discuss at 
> lists.onap.org
> Subject: Re: [onap-discuss] [demo] ONAP Demo Vanilla OpenStack - .env values 
> questions
> 
> *** Security Advisory: This Message Originated Outside of AT&T ***.
> Reference http://cso.att.com/EmailSecurity/IDSP.html for more information.
> 
> Hello Aimee,
> 
> 
> 
> Ubuntu 14.04 and 16.04 are the two Operating Systems that we are using in 
> ONAP. The image name is parametrized in the heat template and environment 
> file, as you pointed out. This is necessary because private OpenStack 
> deployments may have different image names for the same Operating Systems. 
> These names are chosen by users, as such we don?t have any control over them 
> and we can?t make any assumption.
> 
> 
> 
> As such, the names that you will need to use for ubuntu_***_image depend on 
> your specific OpenStack deployment.
> 
> 
> 
> I tried to search the problem that you experienced on the web, and it seems 
> that it can be related to many things, from incorrect installation of 
> glance.image contraints to bugs in some older OpenStack release. The Heat 
> template has been tested with OpenStack Mitaka, heat_template_version: 
> 2015-10-15.
> 
> 
> 
> You may also try to use the image ID instead of the name, and see if that 
> works.
> 
> 
> 
> Thanks,
> 
> Marco
> 
> 
> 
> 
> 
> On 4/7/17, 2:43 PM, "onap-discuss-bounces at lists.onap.org on behalf of 
> Aimee Ukasick" <onap-discuss-bounces at lists.onap.org on behalf of 
> aimeeu.opensource at gmail.com> wrote:
> 
> 
> 
>     Hi all - I'm trying to get the demo running on upstream OpenStack. I'm
> 
>     using the onap_openstack.env and onap_openstack.yaml files pulled today
> 
>     (Friday 7 April 13:00 US CDT).
> 
>     My question is what the value should be for ubuntu_***_image keys in
> 
>     onap_openstack.env.
> 
>     
> 
>     The demo README file L137-138 states:
> 
>         ubuntu_1404_image: PUT THE UBUNTU 14.04 IMAGE NAME HERE
> 
>         ubuntu_1604_image: PUT THE UBUNTU 16.04 IMAGE NAME HERE
> 
>     
> 
>     I have the following images created:
> 
>     root at 6a06e46ee4a8:/tmp/osclient# openstack image list -f json
> 
>     [
> 
>       {
> 
>         "Status": "active",
> 
>         "ID": "ea2d9961-5634-4db0-a685-1a3e4cb0459f",
> 
>         "Name": "cirros-0.3.5-x86_64-disk"
> 
>       },
> 
>       {
> 
>         "Status": "active",
> 
>         "ID": "307e0b0a-c10b-4001-a83a-939e6442d324",
> 
>         "Name": "trusty-server-cloudimg-amd64-disk1"
> 
>       },
> 
>       {
> 
>         "Status": "active",
> 
>         "ID": "6b2485f0-5490-4cbd-9be7-af194d3cbc26",
> 
>         "Name": "xenial-server-cloudimg-amd64-disk1"
> 
>       }
> 
>     ]
> 
>     
> 
>     So in my onap_openstack.env I put:
> 
>     
> 
>     ubuntu_1404_image: trusty-server-cloudimg-amd64-disk1
> 
>     
> 
>     ubuntu_1604_image: xenial-server-cloudimg-amd64-disk1
> 
>     
> 
>     When I try to create the stack:
> 
>     root at 6a06e46ee4a8:/tmp/osclient# openstack stack create ONAP -t
> 
>     onap_openstack.yaml -e onap_openstack.env
> 
>     
> 
>     ERROR: Property error: : resources.dcae_c_vm.properties.image: :
> 
>     "trusty-server-cloudimg-amd64-disk1" does not validate glance.image
> 
>     (constraint not found)
> 
>     
> 
>     ERROR: Property error: : resources.mso_vm.properties.image: :
> 
>     "xenial-server-cloudimg-amd64-disk1" does not validate glance.image
> 
>     (constraint not found)
> 
>     
> 
>     and so on....
> 
>     
> 
>     -----------------------------------------------------------
> 
>     
> 
>     What am I doing wrong? What values should be used for ubuntu_***_image?
> 
>     
> 
>     Also, what version of OpenStack was the vanilla OpenStack Heat templated
> 
>     tested against? Maybe there have been changes between the tested version
> 
>     and the one I'm using.
> 
>     
> 
>     Thanks in advance!
> 
>     
> 
>     
> 
>     ----------------
> 
>     Aimee Ukasick
> 
>     
> 
>     _______________________________________________
> 
>     onap-discuss mailing list
> 
>     onap-discuss at lists.onap.org
> 
>     
> https://urldefense.proofpoint.com/v2/url?u=https-3A__lists.onap.org_mailman_listinfo_onap-2Ddiscuss&d=DwICAg&c=LFYZ-o9_HUMeMTSQicvjIg&r=KgFIQiUJzSC0gUhJaQxg8eC3w16GC3sKgWIcs4iIee0&m=8e7CYMOTTS_YXygAnYkS2MbFMgKliVzIrpXLk02Xiak&s=Ffl8fFPBsXAAcB7oSyJuTZKDxyEzozAbiGMw5pBiCkk&e=
>  
> 
>     
> 
> 
> 
> _______________________________________________
> onap-discuss mailing list
> onap-discuss at lists.onap.org
> https://urldefense.proofpoint.com/v2/url?u=https-3A__lists.onap.org_mailman_listinfo_onap-2Ddiscuss&d=DwIGaQ&c=LFYZ-o9_HUMeMTSQicvjIg&r=2wwdGZ3YcpSivQ2Kio028A&m=9YFt0HHvSELG_pUN7GIr5ylbWS4BvJY_6__Qv0gJy5U&s=7yOoUZtrrwOsXXY4v6WKMw0NKRC15xlyBJkFGuQYvG8&e=
>  
> 

Reply via email to