Hi Alex, have you tried to see if 2.01-41 (March 17th) does have this fix committed?
________________________________ From: Users [[email protected]] on behalf of Alex Walker [[email protected]] Sent: 15 June 2015 14:51 To: Alex Walker; [email protected] Subject: Re: [Users] Service Instance not launching Hi all, Can anyone tell me when an updated package is likely to hit the juniper.net download area? That latest version there is v2.1 build 39 (from March 4th 2015) Many thanks, Alex. From: Users [mailto:[email protected]] On Behalf Of Alex Walker Sent: 27 May 2015 20:02 To: Praneet Bachheti; [email protected] Subject: Re: [Users] Service Instance not launching Thanks Praneet, I'll give it a try. Alex. ________________________________ From: Praneet Bachheti <[email protected]<mailto:[email protected]>> Sent: 27 May 2015 17:22 To: Alex Walker; [email protected]<mailto:[email protected]> Subject: Re: [Users] Service Instance not launching Hi Alex, This is an old issue which has been fixed in later releases. Can you try R2.1 – 56 (the latest). From: Alex Walker <[email protected]<mailto:[email protected]>> Date: Wednesday, May 27, 2015 at 7:03 AM To: "[email protected]<mailto:[email protected]>" <[email protected]<mailto:[email protected]>> Subject: [Users] Service Instance not launching Hi all, I’m having a play with Service Chains via Heat (for some random reason ;). Whilst my networks, service chain and policy appears to create correctly (as seen via the GUI), it fails to launch an instance VM via Nova. Based on the template in /usr/lib/heat/template/service_chain.yaml and associated .env file (modifying to use an already created (and working) Service Template, and adding the apparent syntax change to add ports to the policy), I can create two the described networks, and create the Service Instance and Policy. I see this Service Instance in the Contrail GUI - but it just sits at "spawning" and doesn't launch an VM via Nova. Here's the thing I notice though: * In the Contrail GUI, the heat-created Service Instance shows the associated networks via their UUID, not name - e.g. "Management Network : Automatic,Left Network : 3bf36d7d-59aa-4882-8ca3-2d4eb1d19b9b,Right Network : 325c1b41-cc06-43d4-a3ee-31a48b615066" (the UUIDs are correct) * If I modify the .yaml file to set all networks to be "auto" (instead of the heat-created networks), the heat-created Service Instance then launches a VM via nova OK. * If I manually launch the Service Instance via the GUI (with the same parameters), the instance launches a VM OK (with the Service Instance networks shown by name, not UUID as per the heat-launched instance) Can anyone please shed any light? No matter what I try, I cannot get heat to launch a Service Instance VM. I think this is something to do with the name/UUID of the networks not being right, but can't get any further. I've tried many examples from github etc (using combinations of get_param and get_resource for the networks), but all either suffer this problem, or the stack "CREATE_FAIL"s I'm running Contrail 2.10-39 on Ubuntu 14.04.1 LTS with 3.13.0-40-generic Many thanks, Alex.
_______________________________________________ Users mailing list [email protected] http://lists.opencontrail.org/mailman/listinfo/users_lists.opencontrail.org
