Ask Your Question

JorgeFranco's profile - activity

2019-09-11 10:33:42 -0600 received badge  Supporter (source)
2019-09-11 10:33:24 -0600 commented answer Octavia LB flavor recommendation for Amphora VMs

Really good answer! Something to add, you should play with the size of the disk. Regarding you have huge amount of connection more or less will be the log size. For heavy production environments, I used to set 5~10GB for disk to avoid maintenance. Obviously this depends on your data backend conf.

2019-08-30 15:08:32 -0600 answered a question octavia controller cant connect to amphora

HI stacks !

I have the same issue and it was driving me crazy. Until I've realized that I was using the master (train) and the variables by default that points to the train configurations. that means it was using the Train octavia.agent on the instances and ended up always in ERROR.

For example:

My env is Stein and I was using the agent for Train and give me the same errors.

Solution:

Set the correct variables as Jhon commented. To go easier go like this, export the variables required to set the versioning and the repo you want to use.

export DIB_REPOREF_amphora_agent=stable/stein
export DIB_REPOLOCATION_amphora_agent=https://opendev.org/openstack/octavia

Be sure to use the stable/ and not the origin/stable/ ones.

stable/ocata
stable/pike
stable/queens
stable/rocky
stable/stein

And normally with opendev repo will work

https://opendev.org/openstack/octavia

Good luck :P

2019-06-13 13:44:53 -0600 answered a question Please specify data store No default data store is defined

Seems like there is no register of your datastore in devstack.

You should try to follow the manual installation doc

https://docs.openstack.org/trove/late...

Normally the default datastore are set, you can try this. Hope this will help you : )

2019-06-13 10:43:27 -0600 answered a question Python learning

As @Bernd mentioned the documentation is a good start. But I will add some of parallel documentation and free courses for this purpose.

  1. Tutorialpoint, is the first option for me when I have to learn or remember something about programming. The python docs were useful for my students when I was teaching as moderator at college. https://www.tutorialspoint.com/python/

  2. Course with online tool for testing for free https://www.codecademy.com/learn/lear...

  3. Good online documentation that explain in an easy way why to use python, how are the easy implementations and provide some good examples on each section https://www.programiz.com/python-prog...

If you want it to learn python for openstack. You can go directly on the documentation and check some uses. https://docs.openstack.org/stein/lang...

If you will be using the basic actions use the openstack client. If not, I will recommend to avoid the use of the python implementation of the openstackclient for python due is still in develpment and can have some missing actions that are in the core of the other clients. https://docs.openstack.org/openstacks...

I recommend to you the use of classes, functions and templates. For templating in python you can use Jinja2 that is the most popular engine http://jinja.pocoo.org/

Hope this will be helpful to you :D

2019-05-11 20:50:56 -0600 answered a question Detach volume from non-existing instance

Hi @ICBetter!

Normally when this happens is due a missing request via your MQ or some event that is not trigered.

If the solution with the state doesn't work after some time, there are several ways to do that. But, the best way I've found was to do it directly from the DB. This solution is a litle bit tricky since it's required to modify 2 entries on the cinder and nova database and then delete the mapping for the volume attached on instance in nova DB.

Steps:

  • Go to a controller node. Access the MariaDB container. Access the Database.
  • Detach volume from cinder and Updated the volume status
    MariaDB [(none)]> use cinder;
    MariaDB [(cinder)]> update cinder.volumes set attach_status='detached',status='available'  where id='$volume_uuid';
  • Changed to nova DB
   MariaDB [(none)]> use nova;
  • Deleted the instance entry for that volume on the mapping table
   MariaDB [(nova)]> delete from block_device_mapping where not deleted and volume_id='$volume_uuid';
  • Finally, updated the nova bootindex on the mapping table for the volume root file system
   MariaDB [(nova)]> update nova.block_device_mapping  set boot_index=0 where not deleted and volume_id='$volume_uuid';

This two links can provide you more information:

https://raymii.org/s/articles/Fix_inc...

https://ask.openstack.org/en/question...

Hope this works for you as worked for me :D

2019-05-11 18:24:43 -0600 answered a question Error when booting instance created from vmdk file

Hi @Gigel! I has some issues while migrating images from VMware to openstack in the past. This errors seems to be related to CentOS/Fedora/RHE images that set the values of the disks to be assigned as /hdx drives instead of .vdx. Somehow the original initramfs got corrupted or didn't have all the necessary to boot on OpenStack. To fix it I've followed this :

  • Create an instance from the image
  • Login to the console
  • Hard reboot the instance and reload the console to login to single mode in the grub menu
  • Select the centos rescue option on the grub menu and edit it to replace ro by rw init=/bin/bash and remove rhg quiet. Ctrl+x to start the VM and once in the bash prompt do the following:
  • mount /dev/vda1 in /boot
  • run command: dracut -fv o by passing specifically the kernel version you are using by default on recue mode dracut -f /boot/initramfs-$(uname -r).img $(uname -r) to rebuild the initramfs
  • reboot the instance /sbin/reboot -f

Hope it is the same issue as mine and it can solve yours. |

Note: most of the modern Linux distributions based on 2.6.27+ linux kernel include the virtio drivers already as standard.

2019-05-11 18:06:14 -0600 answered a question Trove documents is too old

This seems a little bit off. The latest release of the documentations for manual installation is sopported by Stein and it was writen this year. So, it should not be any issue

https://docs.openstack.org/trove/late...

2019-05-11 17:55:23 -0600 answered a question Is the size of image impact rhe size of instance ?

Hi @najeh, issues like this are normally related to the size of the image being too big for the flavor you are using (set of ram vcpu and disk size) as mentioned by @Bernd .

Normally for public clouds, a set of flavors are provided to customer allow them to create their own VMs with them and you provide a set of image that are no grether than the actual size of the disk. All this having in mind that the image are raw images and not compressed images as (qcow, qcow2 and some VHD or VHDX ).

Or for private clouds were you choose your own set of flavor and create them for each of the VMs configurations you require.

From here, you have some options.

  1. Set private flavors for the project you require to create the new image based on this snapshot.
  2. Create volumes with the size you require, then create the VM based on the volume instead of an image.

openstack volume create --image image-id --type Type-ID --size Size greater than the actual image name

openstack server create --flavor ID --volume VolumeID --key-name KeyName --nic net-id=NetID Name

2019-05-03 19:01:26 -0600 answered a question No log after instanciation

Can you check inside the instance you are using if the file /etc/default/grub has the following values:

If centos/fedora:

/console=tty0 console=ttyS0,115200n8/

If debian/ubuntuL

console=tty1 console=ttyS0

If that is the case add it into GRUB_CMDLINE_LINUX_DEFAULT variable at the end and reconfigure the grub:

Centos/Fedora: grub2-mkconfig -o /boot/grub2/grub.cfg

Debian/Ubuntu: sudo update-grub

2019-05-03 09:53:49 -0600 commented answer VNC console in dashboard failed to connect to server (code: 1006)

That's good to know :D

2019-03-15 11:19:56 -0600 received badge  Editor (source)
2019-03-15 11:15:35 -0600 answered a question VNC console in dashboard failed to connect to server (code: 1006)

Have you installed the VNC proxy server on the compute servers?

https://access.redhat.com/documentati...

If yes, You should have on both controller and compute the following:

novncproxy_host=$host
novncproxy_port=$port
enabled = true // optional
server_listen = $my_ip
server_proxyclient_address = $my_ip

And for compute servers at the end of the line the following:

novncproxy_base_url = http://controller:<port>/vnc_auto.html

That should work. hopefully :D

2019-03-15 10:48:04 -0600 commented answer see number of free floating ips?

@Vinoth, Yes is completely supported by Mitaka https://docs.openstack.org/mitaka/net...

2019-01-30 22:43:31 -0600 received badge  Teacher (source)
2019-01-30 22:43:31 -0600 received badge  Necromancer (source)
2018-06-24 19:23:10 -0600 answered a question see number of free floating ips?

Hi there!. Just to leave a straight answer for this (I know someday I will need to find it again). Neutron can display all the amount of floating IP in the pools on each network. You only need to list and see all the IP on the networks with:

 - neutron net-ip-availability-list

If you need to check an specific network on a massive list, you can list and run grep using pipe with the network name.

If you want more info like the project id or the subnet availability (if you have more of 1 pool) you can use the following command:

 - neutron net-ip-availability-show <Network ID>
2018-06-06 12:21:28 -0600 received badge  Enthusiast
2018-06-05 13:49:23 -0600 received badge  Autobiographer