On 11/11/2016 01:20 PM, Luis Gomez wrote: > I guess LF people are more suitable to answer here but my understanding is > even when ODL uses OpenStack based cloud > (rackspace), this cloud is currently being handled in Jenkins (not robot) > using packer (not HEAT) definition [1].
To me I think David is asking about the openstack environment we deploy in our system test, like the netvirt openstack jobs. if so, see inline... > BR/Luis > > [1] > https://git.opendaylight.org/gerrit/gitweb?p=releng/builder.git;a=tree;f=packer > >> On Nov 11, 2016, at 3:44 AM, David Lopez Muñoz >> <[email protected] <mailto:[email protected]>> >> wrote: >> >> Hi all, >> >> we are trying to implement *robotframework tests for CSIT environments >> involving Openstack,* meaning invocations to >> neutron, nova, etc. >> >> A reasonable way to implement those tests is by encapsulating multiple >> configurations of networks, routers, ports etc, >> into *HEAT templates,* making it very easy to deploy and undeploy those >> resources. >> >> Perhaps we are wrong, but we didn’t find any keywords in the csit/libraries >> for managing heat invocations. Not a problem, >> since we can easily implement and contribute those keywords. right, we have nothing heat related in our current robot libraries/suites. >> So, we would like to ask about the points: >> · Do you mind having tests using HEAT for their configuration? As long as it's providing some different and/or better aproach, it's all welcome. >> · Is the current deployment defined for openstack including HEAT as >> one of the preinstalled openstack services, >> ready to be used by the robotframework tests? >> · If not, is it reasonable to prepare that environments to have HEAT? we use devstack to deploy openstack. It *might* be as simple as adding the heat service(s) here: https://github.com/opendaylight/releng-builder/blob/master/jjb/netvirt/netvirt-legacy-csit-1node-multi-openstack.yaml#L49 you can easily test this in the sandbox. looking forward to the contributions. JamO >> Regards >> david >> _______________________________________________ >> integration-dev mailing list >> [email protected] >> <mailto:[email protected]> >> https://lists.opendaylight.org/mailman/listinfo/integration-dev > > > > _______________________________________________ > integration-dev mailing list > [email protected] > https://lists.opendaylight.org/mailman/listinfo/integration-dev > _______________________________________________ infrastructure mailing list [email protected] https://lists.opendaylight.org/mailman/listinfo/infrastructure
