Ask Your Question

raimonbosch's profile - activity

2020-07-01 14:13:59 -0600 received badge  Popular Question (source)
2020-07-01 14:13:59 -0600 received badge  Famous Question (source)
2020-07-01 14:13:59 -0600 received badge  Notable Question (source)
2019-10-17 03:30:40 -0600 received badge  Famous Question (source)
2019-10-17 03:30:40 -0600 received badge  Notable Question (source)
2017-08-22 12:02:59 -0600 received badge  Popular Question (source)
2017-04-25 08:50:27 -0600 received badge  Famous Question (source)
2017-03-01 16:01:10 -0600 received badge  Famous Question (source)
2017-01-16 09:18:37 -0600 commented question Change cidr mask on existing network? (add fixed ips)

I have tried to update manually on the DB to /27 and restart all but the error persists. In the documentation there is no network-update option. So no idea how to proceed here.

2017-01-16 08:07:39 -0600 asked a question Change cidr mask on existing network? (add fixed ips)

Hi,

I'm running Openstack Juno version with nova-network

> nova network-list 
+--------------------------------------+----------+---------------+
| ID                                   | Label    | Cidr          |
+--------------------------------------+----------+---------------+
| b8304c38-ee55-452b-821e-d96a0a4ccccc | demo-net | 172.16.0.0/29 |
+--------------------------------------+----------+---------------+

The problem with this Cidr mask 172.16.0.0/29 is that only has 8 IPs and 6 of them are already being used for admin purposes so my question is how can I update this record to add more fixed IPs?

Thanks in advance,

2017-01-12 10:16:29 -0600 asked a question What are the side effects of running several compute nodes on the same host? (pointing to the same Hypervisor)

Hi all,

We have a use case where we use Openstack for an ARM board (https://www.arm.com/products/tools/de...). As you will see this board has two kinds of processors inside so it is needed to do some kind of abstraction to avoid spinning up VMs to the wrong kind of processor.

My question is if it is feasible to run two compute nodes: one pinned to the BIG cpus and a second pinned to the LITTLE cpus. This way we will work with two instances where each one holds one kind of CPU. In case this is possible which things do we need to have in mind to make this configuration work?

Thanks in advance,

FYI, we work with Juno version so a patch is needed to support http://specs.openstack.org/openstack/...

2016-12-02 02:55:46 -0600 received badge  Notable Question (source)
2016-12-02 02:55:46 -0600 received badge  Popular Question (source)
2016-11-07 09:57:32 -0600 received badge  Famous Question (source)
2016-09-22 10:06:20 -0600 commented answer Cannot setup network: Cannot find any PID under container

@holger-king The problem is that nova-docker does not send any parameter to the container. So you have to provide some kind of logic to your container to work without the "/bin/bash" parameter.

2016-09-22 05:06:54 -0600 edited answer Cannot setup network: Cannot find any PID under container

Ok,

Again answering myself my questions. This particular docker container was not supposed to be running permanently. The nova-docker driver somehow tries to look for a pid associated to this container. If the container has already finished his job to do, then it can't be registered to Openstack.

So my dirty solution was to add something like that on my docker-entrypoint.sh:

if [ "$@" ]

then

exec "$@"

else

echo "Container running!"

sleep 3h

fi

So when I start this container without parameters (which is the case of nova-docker), I just sleep so everyone knows that this container has to be registered on OpenStack and nothing fails.

I guess that it would be good to give support to this kind of containers on nova-docker. If not, it is necessary to perform hacks like this in all your containers.

Cheers,

EDIT: You can add your entrypoint at the end of the Dockerfile. Make sure that it is located in the same folder that your Dockerfile:

COPY docker-entrypoint.sh /entrypoint.sh

RUN chmod +x /entrypoint.sh

ENTRYPOINT ["/entrypoint.sh"]

EXPOSE 80 22 30000-60000

2016-09-22 04:54:02 -0600 commented answer Cannot setup network: Cannot find any PID under container

@holger-king In my case the containers where not found because they were stopping early. That should not happen very often. @giang: The entrypoint is usually defined at the end of the Dockerfile.

2016-08-31 10:34:16 -0600 marked best answer Cannot setup network: Cannot find any PID under container

Hi,

I am using nova-docker to run docker containers from Openstack. Some of my containers are not able to setup network and they give this error: Cannot setup network: Cannot find any PID under container

I have already tried to set tty:True on the driver.py and it still fails. When I fire up those docker by using "docker run -it --net bridge ..." everything works fine. I guess that there is a problem assigning the correct network on nova-docker.

Thanks in advance,

2016-02-22 10:22:34.400 5146 WARNING novadocker.virt.docker.driver [req-c29f063d-f54b-44d1-b608-82face013275 bdc8aedaf84b4ed8a8d2659928a3d0af 3407b066d1f542668f70715d5597a680 - - -] [instance: f0c9868f-3753-4ba7-b8ad-dc5e8e728bc6] Cannot setup network: Cannot find any PID under container "79520cf58bfad8770399b86844513369ae42b7e33b100245f45101df1905ee7a"
2016-02-22 10:22:34.400 5146 TRACE novadocker.virt.docker.driver [instance: f0c9868f-3753-4ba7-b8ad-dc5e8e728bc6] Traceback (most recent call last):
2016-02-22 10:22:34.400 5146 TRACE novadocker.virt.docker.driver [instance: f0c9868f-3753-4ba7-b8ad-dc5e8e728bc6]   File "/usr/local/lib/python2.7/dist-packages/novadocker/virt/docker/driver.py", line 406, in _start_container
2016-02-22 10:22:34.400 5146 TRACE novadocker.virt.docker.driver [instance: f0c9868f-3753-4ba7-b8ad-dc5e8e728bc6]     self._attach_vifs(instance, network_info)
2016-02-22 10:22:34.400 5146 TRACE novadocker.virt.docker.driver [instance: f0c9868f-3753-4ba7-b8ad-dc5e8e728bc6]   File "/usr/local/lib/python2.7/dist-packages/novadocker/virt/docker/driver.py", line 214, in _attach_vifs
2016-02-22 10:22:34.400 5146 TRACE novadocker.virt.docker.driver [instance: f0c9868f-3753-4ba7-b8ad-dc5e8e728bc6]     raise RuntimeError(msg.format(container_id))
2016-02-22 10:22:34.400 5146 TRACE novadocker.virt.docker.driver [instance: f0c9868f-3753-4ba7-b8ad-dc5e8e728bc6] RuntimeError: Cannot find any PID under container "79520cf58bfad8770399b86844513369ae42b7e33b100245f45101df1905ee7a"
2016-02-22 10:22:34.400 5146 TRACE novadocker.virt.docker.driver [instance: f0c9868f-3753-4ba7-b8ad-dc5e8e728bc6] 
2016-02-22 10:22:34.421 5146 ERROR nova.compute.manager [req-c29f063d-f54b-44d1-b608-82face013275 bdc8aedaf84b4ed8a8d2659928a3d0af 3407b066d1f542668f70715d5597a680 - - -] [instance: f0c9868f-3753-4ba7-b8ad-dc5e8e728bc6] Instance failed to spawn
2016-02-22 10:22:34.421 5146 TRACE nova.compute.manager [instance: f0c9868f-3753-4ba7-b8ad-dc5e8e728bc6] Traceback (most recent call last):
2016-02-22 10:22:34.421 5146 TRACE nova.compute.manager [instance: f0c9868f-3753-4ba7-b8ad-dc5e8e728bc6]   File "/usr/lib/python2.7/dist-packages/nova/compute/manager.py", line 2473, in _build_resources
2016-02-22 10:22:34.421 5146 TRACE nova.compute.manager [instance: f0c9868f-3753-4ba7-b8ad-dc5e8e728bc6]     yield resources
2016-02-22 10:22:34.421 5146 TRACE nova.compute.manager [instance: f0c9868f-3753-4ba7-b8ad-dc5e8e728bc6]   File "/usr/lib/python2.7/dist-packages/nova/compute/manager.py", line 2345, in _build_and_run_instance
2016-02-22 10:22:34.421 5146 TRACE nova.compute.manager [instance: f0c9868f-3753-4ba7-b8ad-dc5e8e728bc6]     block_device_info=block_device_info)
2016-02-22 10:22:34.421 5146 TRACE nova.compute.manager [instance: f0c9868f-3753-4ba7-b8ad-dc5e8e728bc6]   File "/usr/local/lib/python2.7/dist-packages/novadocker/virt/docker/driver.py", line 449, in spawn
2016-02-22 10:22:34.421 5146 TRACE nova.compute.manager [instance: f0c9868f-3753-4ba7-b8ad-dc5e8e728bc6]     self._start_container(container_id, instance, network_info)
2016-02-22 10:22:34.421 5146 TRACE nova.compute.manager [instance: f0c9868f-3753-4ba7-b8ad-dc5e8e728bc6]   File "/usr/local/lib/python2.7/dist-packages/novadocker/virt/docker/driver.py", line 414, in _start_container
2016-02-22 10:22:34.421 5146 TRACE nova.compute.manager [instance: f0c9868f-3753-4ba7-b8ad-dc5e8e728bc6]     instance_id=instance['name'])
2016-02-22 10:22:34.421 5146 TRACE nova.compute.manager [instance: f0c9868f-3753-4ba7-b8ad-dc5e8e728bc6] InstanceDeployFailure: Cannot setup network: Cannot find any PID under container "79520cf58bfad8770399b86844513369ae42b7e33b100245f45101df1905ee7a
2016-04-22 03:29:25 -0600 commented answer How to enable passwordless ssh between the instances?

you can use plain shell scripting. Something like echo "YOUR_PUBLIC_KEY" >> ~/.ssh/authorized_keys and set all the permissions accordingly. Here you have some tips: http://sshkeychain.sourceforge.net/mi...

2016-04-19 10:12:49 -0600 asked a question How can I get disk information about an hypervisor?

Hi,

I need to know dynamically if the disk provided by an hypervisor is RAID or SSD. Is there a method to achieve that?

Thanks in advance,

2016-04-18 09:55:47 -0600 marked best answer How should I configure Openstack network interfaces?

Hi,

I'm following OpenStack's installation guide for Ubuntu but I don't get a clear idea how should I modify our /etc/network/interfaces files in order to comply with OpenStack's requirements:

http://docs.openstack.org/liberty/install-guide-ubuntu/environment-networking-controller.html (http://docs.openstack.org/liberty/ins...)

What I understand until now is that I have to set up at least two network interfaces (one for the controller and another one for the compute node). By now, our installation shouldn't be very complicated since we are installing everything in a single node to run some tests. So to my understanding we only need to set up a network for internal communication between nodes and a second to make nodes reachable.

http://docs.openstack.org/liberty/install-guide-ubuntu/environment-networking.html (http://docs.openstack.org/liberty/ins...)

Someone with a similar configuration can share how this /etc/network/interfaces should look like?

2016-04-18 09:55:28 -0600 received badge  Notable Question (source)
2016-04-18 09:51:20 -0600 answered a question How to enable passwordless ssh between the instances?

When you deploy a new instance on the tab "Access & Security" you can choose a keypair. I guess that if you choose the same keypair for all instances, they will get connectivity between them. If that does not work, you could also set up an initialization script on "Post-Creation" tab and modify ~/.ssh/authorized_keys

2016-04-18 09:42:16 -0600 asked a question How can I get all hardware information through OpenStack API?

Hi,

I would like to see the disk type and the cpu type of each of my hostnames. It would be even better if I could see all the hardware information that you could see via 'lshw' command so we don't miss anything.

the most similar thing I have found is: GET /v2.1/​{tenant_id}​/os-hypervisors/​{hypervisor_id}​

but here I don't have all the details about disk, for instance. What parts of the code must be changed to include this information? Is there any ongoing patch?

2016-04-15 05:48:25 -0600 received badge  Famous Question (source)
2016-03-30 08:00:02 -0600 commented answer How to configure an existing Kolla OpenStack installation to enable Docker

The permissions inside the docker container have to be handled on your Dockerfile. There you can specify your users and your passwords.

2016-03-23 10:33:19 -0600 marked best answer Resize is ignored

Hi,

We have found some cases where api call to resize returns a 202 http://developer.openstack.org/api-ref-compute-v2.1.html#resize but it does nothing. In this cases seems like the resize is scheduled, but it is never performed. So the machine keeps in ACTIVE state and no vertical scalability is performed. The easiest way to reproduce the error is by performing a scale down operation i.e. from m1.small to m1.tiny.

Is this a known issue?

This happens with 2014.1.5 (Icehouse) version. The logs don't show any errors aside from some WARNINGS on nova-scheduler.log.

Thanks in advance,

2016-03-23 10:33:10 -0600 answered a question Resize is ignored

The problem was on the way we were deploying our virtual machines. For some reason we were using "nova" as default availability zone in a cluster that didn't have a "nova" availability zone.

So for instance if you deploy a VM in a hostname named server01, you would deploy as availabilityZone="nova:server01". That somehow was causing the problem but not at the moment of deploy, but at the moment of resize. Once I solved the problem by passing its proper availability zone to each node i.e. availabilityZone="availabilityZone01:sever01" the problem was gone.

It was useful to use tcpdump to track the activity of OpenStack's API and check what was really being sent there.

2016-03-23 06:40:55 -0600 received badge  Student (source)