[openstack-dev] How to specify gic version in openstack
Hi, I am trying to run Openstack on ARM64 architecture. ARM64 architecture with KVM hypervisor needs GIC version(generic interrupt controller) as a property for the image when we are creating/uploading an image. I would like to include this property in the glance code. I am new to glance, Can someone suggest me how to approach for this. Thanks in advance -Vishnu __ OpenStack Development Mailing List (not for usage questions) Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
[openstack-dev] [Openstack-dev][Tacker] Not able to run user_data commands on my instance
Hi, I'm have installed openstack with tacker by devstack. I'm able to run OpenWRT vnf and able to configure the firewall service with openwrt management driver. And also able to run shell commands in cirros image which is also using openwrt management driver. Now I have created one ubuntu image, and able to launch through tacker. In this instance i want run some shell commands through tacker's user_data feature. But no commands are executing. Is it possible to run commands on custom images unlike cirros/openwrt? If yes kindly share the procedure to create proper ubuntu image. Below is tosca configd file tosca_definitions_version: tosca_simple_profile_for_nfv_1_0_0 description: Demo with user-data metadata: template_name: sample-vnfd-userdata topology_template: node_templates: VDU1: type: tosca.nodes.nfv.VDU.Tacker capabilities: nfv_compute: properties: num_cpus: 1 mem_size: 1024 MB disk_size: 1 GB properties: image: ubuntu-image config: | param0: key1 param1: key2 mgmt_driver: openwrt config_drive: true user_data_format: RAW user_data: | #!/bin/sh echo "my hostname is `hostname`" > /tmp/hostname date > /tmp/date ifconfig > /tmp/ifconfig df -h > /tmp/diskinfo CP1: type: tosca.nodes.nfv.CP.Tacker properties: management: true order: 0 anti_spoofing_protection: false requirements: - virtualLink: node: VL1 - virtualBinding: node: VDU1 VL1: type: tosca.nodes.nfv.VL properties: network_name: net_mgmt vendor: ACME Regards, -Vishnu __ OpenStack Development Mailing List (not for usage questions) Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
[openstack-dev] [Openstack-dev][Tacker] How to update vnf with user_data
Hi, Someone can help me to update vnf with user_data by using noop or openwrt mgmt_driver. Below is my tosca-config-user-data.yaml vdus: VDU1: config: user_data: | #!/bin/sh echo "my hostname is `hostname`" > /tmp/hostname df -h > /tmp/diskinfo Regards, -vishnu __ OpenStack Development Mailing List (not for usage questions) Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
[openstack-dev] [tacker] VNF Configuration injection issue
Hi, I'm running tacker and able to launch vnf through VNF manager. But the configuration of the VNF is not getting injected to VNF. Kindly help me in debugging of injection of configuration Please find below tosca config file tosca_definitions_version: tosca_simple_profile_for_nfv_1_0_0 description: OpenWRT with firewall services metadata: template_name: APM topology_template: node_templates: VDU1: type: tosca.nodes.nfv.VDU.Tacker capabilities: nfv_compute: properties: num_cpus: 1 mem_size: 1024 MB disk_size: 1 GB properties: image: openWRT-image2 config: firewall: | package firewall config defaults option syn_flood '1' option input 'ACCEPT' option output 'ACCEPT' option forward 'REJECT' config zone option name 'lan' list network 'lan' option input 'ACCEPT' option output 'ACCEPT' option forward 'REJECT' config zone option name 'wan' list network 'wan' list network 'wan6' option input 'REJECT' option output 'ACCEPT' option forward 'REJECT' option masq '1' option mtu_fix '1' config forwarding option src 'lan' option dest 'wan' config rule option name 'Allow-DHCP-Renew' option src 'wan' option proto 'udp' option dest_port '68' option target 'ACCEPT' option family 'ipv4' config rule option name 'Allow-Ping' option src 'wan' option proto 'icmp' option icmp_type 'echo-request' option family 'ipv4' option target 'REJECT' mgmt_driver: openwrt monitoring_policy: name: ping parameters: count: 3 interval: 10 actions: failure: respawn CP1: type: tosca.nodes.nfv.CP.Tacker properties: management: true anti_spoofing_protection: false requirements: - virtualLink: node: VL1 - virtualBinding: node: VDU1 VL1: type: tosca.nodes.nfv.VL properties: network_name: net_mgmt vendor: Tacker Note: haven't seen any ssh connection formed to VNF from host during and after installation. Thanks && Regards, -Vishnu __ OpenStack Development Mailing List (not for usage questions) Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
Re: [openstack-dev] [Heat] Precursor to Phase 1 Convergence
Steve, Auto recovery is the plan. Engine failure should be detected by way of heartbeat or recover partially realised stack on engine startup in case of a single engine scenario. --continue command was just a additional helper api. [image: --] Visnusaran Murugan [image: http://]about.me/ckmvishnu http://about.me/ckmvishnu?promo=email_sig On Thu, Jan 8, 2015 at 11:29 PM, Steven Hardy sha...@redhat.com wrote: On Thu, Jan 08, 2015 at 09:53:02PM +0530, vishnu wrote: Hi Zane, I was wondering if we could push changes relating to backup stack removal and to not load resources as part of stack. There needs to be a capability to restart jobs left over by dead engines.A something like heat stack-operation --continue [git rebase --continue] To me, it's pointless if the user has to restart the operation, they can do that already, e.g by triggering a stack update after a failed stack create. The process needs to be automatic IMO, if one engine dies, another engine should detect that it needs to steal the lock or whatever and continue whatever was in-progress. Had a chat with shady regarding this. IMO this would be a valuable enhancement. Notification based lead sharing can be taken up upon completion. I was referring to a capability for the service to transparently recover if, for example, a heat-engine is restarted during a service upgrade. Currently, users will be impacted in this situation, and making them manually restart failed operations doesn't seem like a super-great solution to me (like I said, they can already do that to some extent) Steve ___ OpenStack-dev mailing list OpenStack-dev@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev ___ OpenStack-dev mailing list OpenStack-dev@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
[openstack-dev] [Heat] Precursor to Phase 1 Convergence
Hi Zane, I was wondering if we could push changes relating to backup stack removal and to not load resources as part of stack. There needs to be a capability to restart jobs left over by dead engines. something like heat stack-operation --continue [git rebase --continue] Had a chat with shady regarding this. IMO this would be a valuable enhancement. Notification based lead sharing can be taken up upon completion. Your thoughts. -Vishnu irc: ckmvishnu ___ OpenStack-dev mailing list OpenStack-dev@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
