Ask Your Question

boniamd's profile - activity

2016-03-16 23:42:06 -0500 received badge  Popular Question (source)
2016-03-16 23:42:06 -0500 received badge  Famous Question (source)
2016-03-16 23:42:06 -0500 received badge  Notable Question (source)
2016-01-26 12:45:13 -0500 received badge  Famous Question (source)
2016-01-05 14:33:20 -0500 received badge  Notable Question (source)
2016-01-05 12:54:58 -0500 received badge  Notable Question (source)
2015-12-28 20:28:54 -0500 received badge  Popular Question (source)
2015-12-20 08:24:05 -0500 received badge  Enthusiast
2015-12-11 05:29:14 -0500 received badge  Student (source)
2015-12-11 02:27:33 -0500 asked a question instance not able to attach shared network

Hi There,

I have a shared neutron network owned by admin tenant (i check the shared option), and I try to deploy an instance in other tenant, i can see the network and select in as part of instance deployment.

When the deployment complete, apparently the NIC is not attached in the VM (i check it from the hypervisor level). There is a blog stating a similar problem here: https://www.s3it.uzh.ch/blog/openstack-neutron-vlan/ (https://www.s3it.uzh.ch/blog/openstac...) , but apparently their issue only affects when they share an external network.

I use default nova/policy.json Anyone have idea on what to check?

Thank you

2015-12-10 05:16:49 -0500 received badge  Popular Question (source)
2015-12-03 09:10:07 -0500 asked a question automate join domain for windows instance

Hi There, I'd like to ask if there are practices to automate join domain on the windows instances launched from openstack. What do you guys usually do? any working template of unattend.xml to join domain?

I've tried to prepare windows image, install cloudbase init, and sysprep it, and i insert the unattend.xml via openstack configuration drive. However there is no luck, the instance fails to complete the installation, with the Panther setuperr.log like the following (unattended join: netjoindomain attempt failed: 0x35) https://pbs.twimg.com/media/CVTbyJvUAAEh8f_.png:large (image description)

I encountered this issue specific in automating join domain when deployed from openstack, when i try my unattend.xml directly on the hypervisor, it can do the job.

Below is my unattend.xml

   <?xml version="1.0" encoding="utf-8"?>
<unattend xmlns="urn:schemas-microsoft-com:unattend">
 <settings pass="windowsPE">
  <component name="Microsoft-Windows-International-Core-WinPE" processorArchitecture="amd64" publicKeyToken="31bf3856ad364e35" language="neutral" versionScope="nonSxS" xmlns:wcm="http://schemas.microsoft.com/WMIConfig/2002/State" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
            <SetupUILanguage>
                <UILanguage>en-US</UILanguage>
            </SetupUILanguage>
            <InputLocale>0409:00000409</InputLocale>
            <SystemLocale>en-US</SystemLocale>
            <UILanguage>en-US</UILanguage>
            <UILanguageFallback>en-US</UILanguageFallback>
            <UserLocale>en-US</UserLocale>
            <UserData>
                <ProductKey>
                    <Key>VDNYM-JBKJ7-DC4X9-BT3QR-JHRGY</Key>
                    <WillShowUI>Never</WillShowUI>
                </ProductKey>
                <AcceptEula>true</AcceptEula>
                <FullName>VG Admin</FullName>
                <Organization>VinGroup JSC</Organization>
            </UserData>

</component>
</settings>
  <settings pass="generalize">
    <component name="Microsoft-Windows-PnpSysprep" processorArchitecture="amd64" publicKeyToken="31bf3856ad364e35" language="neutral" versionScope="nonSxS" xmlns:wcm="http://schemas.microsoft.com/WMIConfig/2002/State" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
      <PersistAllDeviceInstalls>true</PersistAllDeviceInstalls>
    </component>
  </settings>

<settings pass="oobeSystem">
        <component name="Microsoft-Windows-International-Core" processorArchitecture="amd64" publicKeyToken="31bf3856ad364e35" language="neutral" versionScope="nonSxS" xmlns:wcm="http://schemas.microsoft.com/WMIConfig/2002/State" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
            <SystemLocale>en-US</SystemLocale>
            <UILanguage>en-US</UILanguage>
            <UserLocale>en-US</UserLocale>
        </component>
<component name="Microsoft-Windows-Shell-Setup" processorArchitecture="amd64" publicKeyToken="31bf3856ad364e35" language="neutral" versionScope="nonSxS" xmlns:wcm="http://schemas.microsoft.com/WMIConfig/2002/State" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
            <UserAccounts>
                <AdministratorPassword>
                    <Value>P@ssw0rd</Value>
                    <PlainText>true</PlainText>
                </AdministratorPassword>
                <LocalAccounts>
                    <LocalAccount wcm:action="add">
                        <Password>
                            <Value>P@ssw0rd</Value>
                            <PlainText>true</PlainText>
                        </Password>
                        <Description>vgadmin</Description>
                        <DisplayName>vgadmin</DisplayName>
                        <Group>administrators</Group>
                        <Name>vgadmin</Name>
                    </LocalAccount>
                </LocalAccounts>
            </UserAccounts>
            <OOBE>
                <HideEULAPage>true</HideEULAPage>
                <HideWirelessSetupInOOBE>true</HideWirelessSetupInOOBE>
                <NetworkLocation>Home</NetworkLocation>
                <ProtectYourPC>1</ProtectYourPC>
                <HideOnlineAccountScreens>true</HideOnlineAccountScreens>
                <HideLocalAccountScreen>true</HideLocalAccountScreen>
                <SkipUserOOBE>true</SkipUserOOBE>
                <HideOEMRegistrationScreen>true</HideOEMRegistrationScreen>
            </OOBE>
          </component>
  </settings>
<settings pass="specialize">
        <component name="Microsoft-Windows-Shell-Setup" processorArchitecture="amd64" publicKeyToken="31bf3856ad364e35" language="neutral" versionScope="nonSxS" xmlns:wcm="http://schemas.microsoft.com/WMIConfig/2002/State" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
            <ComputerName>*</ComputerName>
        </component>
        <component name="Microsoft-Windows-UnattendedJoin" processorArchitecture="amd64" publicKeyToken="31bf3856ad364e35" language="neutral" versionScope="nonSxS" xmlns:wcm="http://schemas.microsoft.com/WMIConfig/2002/State" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
            <Identification>
                <UnsecureJoin>false</UnsecureJoin>
                <Credentials>
                    <Domain>amd.local</Domain>
                    <Password>P@ssw0rd</Password>
                    <Username>vgadmin</Username>
                </Credentials>
                 <JoinDomain>amd.local</JoinDomain>
            </Identification>
        </component>
    </settings>
</unattend>
2015-11-22 06:22:39 -0500 asked a question heat template - create instance, attach cinder volume, use it as LVM

Hi, I want to create heat template that serve the following purpose:

  1. Launch Instance from image
  2. Create Cinder Volume
  3. Attach the Volume to the instance
  4. Configure the volume on the instance as LVM, format the LVM as ext4, and finally mount it

So i create something like this:

 heat_template_version: 2015-04-30
description: >
  A template showing how to create a Nova instance, a Cinder volume and attach
  the volume to the instance. The template uses only Heat OpenStack native
  resource types.
parameters:
  key_name:
    type: string
    default: linux_key
    description:
      Name of an existing key pair to enable SSH access to the instance.
  instance_type:
    type: string
    description: Type of the instance to be created.
    default: m1.small
    constraints:
      - allowed_values: [m1.small, m1.medium, m1.large]
        description:
          Value must be one of 'm1.small', 'm1.medium' or 'm1.large'.
  image_id:
    type: string
    description: ID of the image to use for the instance to be created.
    default: linux_img
    constraints:
      - allowed_values: [ linux_img ]
        description:
          Image ID must be linux_img
  availability_zone:
    type: string
    description: The Availability Zone to launch the instance.
    default: nova
  volume_size:
    type: number
    description: Size of the volume to be created.
    default: 1
    constraints:
      - range: { min: 1, max: 1024 }
        description: must be between 1 and 1024 Gb.
resources:
  avoltest:
    type: OS::Nova::Server
    properties:
      availability_zone: { get_param: availability_zone }
      image: { get_param: image_id }
      flavor: { get_param: instance_type }
      key_name: { get_param: key_name }
      user_data_format: RAW
      user_data:
        str_replace:
          params:
            $LOGFILE: /tmp/installlog.log
            $VOLSIZE: { get_param: volume_size }
          template: |
            #!/bin/bash -v
              die() {
              _WC-NOTIFY_ --data-binary '{"status": "FAILURE"}'
                exit 1
              }
            yum install -y lvm2 >> $LOGFILE 2>&1 || die
            pvcreate /dev/sdb >> $LOGFILE 2>&1 || die
            vgcreate volgroup01 /dev/sdb >> $LOGFILE 2>&1 || die
            lvcreate -l+100%FREE -n lvol01 volgroup01 >> $LOGFILE 2>&1 || die
            mkfs.ext4 -F /dev/mapper/volgroup01-lvol01 >> $LOGFILE 2>&1 || die
            mkdir /data
            echo "/dev/mapper/volgroup01-lvol01 /data ext4 defaults 0 0" >> /etc/fstab
            mount -a
            df -ah >> $LOGFILE 2>&1 || die
  cinder_volume:
    type: OS::Cinder::Volume
    properties:
      size: { get_param: volume_size }
      availability_zone: { get_param: availability_zone }
  volume_attachment:
    type: OS::Cinder::VolumeAttachment
    properties:
      volume_id: { get_resource: cinder_volume }
      instance_uuid: { get_resource: avoltest }
      mountpoint: /dev/sdb
outputs:
  instance_ip:
    description: Public IP address of the newly created Nova instance.
    value: { get_attr: [avoltest, first_address] }

but with that template, the bash command for creating the lvm (pvcreate and so on) is executed first before the volume is being attached to the instance, so it failed.

Anyone have idea how to make it in order so that the bash commands on the instance will be executed after the volume is attached? Thank you

2014-09-10 09:01:06 -0500 received badge  Famous Question (source)
2014-08-10 11:01:16 -0500 received badge  Notable Question (source)
2014-08-10 04:17:00 -0500 answered a question Unable to login to new instance via console/SSH

Has been solved, similar like this one: https://ask.openstack.org/en/question/44365/neutron-metadata-agent-unexpected-error/ (https://ask.openstack.org/en/question...)

2014-08-10 03:33:26 -0500 commented question Unable to login to new instance via console/SSH

Hi All,

Does the metadata service (in this case the controller node) need to be reachable (can be ping) from the instance?

2014-08-07 01:53:02 -0500 received badge  Popular Question (source)
2014-08-06 05:37:17 -0500 received badge  Editor (source)
2014-08-06 05:37:17 -0500 edited question Unable to login to new instance via console/SSH

I am following this guide ( http://docs.openstack.org/icehouse/install-guide/install/apt/content/ (http://docs.openstack.org/icehouse/in...) ) to start an openstack environment and was able to start a Cirros instance.

However, i can not login to the Cirros Instance using ssh keypair "ssh -i key.pem cirros@ip-address" (it still asking for password, i can login using cirros default password) and observe there is no .ssh/authorized_keys stored in my instance. I thought it was Cirros bug, but i've also tried boot instance using Ubuntu Cloud image and the SSH using keypair is also not working (although i've assign the keypair too)

I'm also tried another means to inject ssh keypair (and also create user at boot time) using examples from http://cloudinit.readthedocs.org/en/latest/topics/examples.html (http://cloudinit.readthedocs.org/en/l...) and use it using --user-data at nova boot, none of them worked (user creation also not working).

Now i am wondering if my environment has the correct configuration to inject ssh keypair or cloud-init files to the newly created instances.

How can i verify? i don't know to begin with. I just want to easily login to my instance by any means (console/SSH)

Update log when booting the instance:

   2014-08-06 10:25:54,216 - util.py[WARNING]: 'http://169.254.169.254/2009-04-04/meta-data/instance-id' failed [0/120s]: http error [500]
2014-08-06 10:25:55,383 - util.py[WARNING]: 'http://169.254.169.254/2009-04-04/meta-data/instance-id' failed [1/120s]: http error [500]
2014-08-06 10:25:56,664 - util.py[WARNING]: 'http://169.254.169.254/2009-04-04/meta-data/instance-id' failed [2/120s]: http error [500]

is there something wrong with my metadata service? it is actually up and running

root@controller:~# lsof -i:8775
COMMAND   PID USER   FD   TYPE DEVICE SIZE/OFF NODE NAME
nova-api 1084 nova    9u  IPv4  13534      0t0  TCP *:8775 (LISTEN)
nova-api 1775 nova    9u  IPv4  13534      0t0  TCP *:8775 (LISTEN)
nova-api 1776 nova    9u  IPv4  13534      0t0  TCP *:8775 (LISTEN)
nova-api 1777 nova    9u  IPv4  13534      0t0  TCP *:8775 (LISTEN)
nova-api 1778 nova    9u  IPv4  13534      0t0  TCP *:8775 (LISTEN)

Also add error message in the network node /etc/neutron/metadata-agent.log

2014-08-06 19:12:23.430 3759 TRACE neutron.agent.metadata.agent     endpoint_type=self.endpoint_type)

2014-08-06 19:12:23.430 3759 TRACE neutron.agent.metadata.agent File "/usr/lib/python2.7/dist-packages/neutronclient/client.py", line 81, in url_for 2014-08-06 19:12:23.430 3759 TRACE neutron.agent.metadata.agent raise exceptions.EndpointNotFound() 2014-08-06 19:12:23.430 3759 TRACE neutron.agent.metadata.agent EndpointNotFound: Could not find Service or Region in Service Catalog. 2014-08-06 19:12:23.430 3759 TRACE neutron.agent.metadata.agent 2014-08-06 19:12:23.432 3759 INFO eventlet.wsgi.server [req-31d4c1ac-0d5d-4f09-ad50-d80a23d362a9 None] 10.0.99.30,<local> - - [06/Aug/2014 19:12:23] "GET /2009-04-04/meta-data/instance-id HTTP/1.1" 500 229 0.201596

I've doublecheck the auth_region is matching with one registered in keystone (RegionOne)