Skip to content

Instantly share code, notes, and snippets.


Block or report user

Report or block praneetb

Hide content and notifications from this user.

Learn more about blocking users

Contact Support about this user’s behavior.

Learn more about reporting abuse

Report abuse
View GitHub Profile

Participants List

List of participants who have paid 100$ deposit towards BiggestLoser2. Money is held With "Praneet Bachheti" until the end of the contest.

 1 Nipa Kumar  
 2 Nachi Ueno  
 3 Aniket Gawade  
 4 Praneet Bachheti  
 5 Nagendra Maynattamai  
 6 Soumil Kulkarni  
View Port Tuple
Release 3.0 onwards, we have introduced port tuples when launching VM services. With this
support, user can create ports and then bind those ports to a service instance.
In R2.x, the service-monitor daemon would create a VM object for each VM based service
instance and create/attach ports to the VM. The VM object was being usedto bind the
VM based service instances to the ports.
In this model, heat engine knew only about the service instance object. The objects created
by the service-monitor daemon (such as VM, ports, ...) were not visible to heat.
We saw issues with this approach and decided on the new design of port-tuples.
View contrail-heat
With Release 3.0, contrail-heat resources/templates are being auto-generated from the Schema.
The generated resources/templates are part of the python-contrail package and located in
/usr/lib/python2.7/dist-packages/vnc_api/gen/heat/ directory. This directory has three sub-directories
1. resources/
This sub-directory contains all the resources for the contrail-heat plugin. It runs in the context
of the heat-engine service.
2. templates/
This sub-directory contains template for each resource. They are sample templates with every possible
You can’t perform that action at this time.