Ask Your Question

kyomster's profile - activity

2017-08-06 05:00:18 -0500 received badge  Enthusiast
2017-08-05 17:14:56 -0500 commented question kolla aio external network with single NIC

I have the same issue. Did you manage to make it work ?

2017-07-31 08:31:01 -0500 commented answer Establishing Instance Internet Connectivity with Kolla

I have the same issue with br-ex and br-tun being down. How did you manage to start those two interfaces ?

2017-06-08 20:45:59 -0500 received badge  Famous Question (source)
2017-05-16 08:57:44 -0500 received badge  Notable Question (source)
2017-05-07 14:55:45 -0500 received badge  Popular Question (source)
2017-05-06 11:10:47 -0500 commented answer RDO TripleO QuickStart Undercloud failed

when I do "virsh list" on VIRTHOST I get

Id Name State


1 undercloud running

2017-05-06 11:08:44 -0500 commented answer RDO TripleO QuickStart Undercloud failed

yes it works without root password requested.

also, I tried twice with 2 different host (one with 32GB memory, the other 60GB memory) hence my bad copy/paste with 2 different IPs in pastebin but good IP was used for deployment

2017-05-06 08:31:21 -0500 commented question RDO TripleO QuickStart Undercloud failed

VIRTHOST is just one host, it's a simple install of CentOS 7.

Workstation is also CentOS 7.

I simply installed 2 CentOS, one on VIRTHOST having 60GB memory and 250GB disk with 10 cores, the other one for workstation.

commands executed on workstation are: https://pastebin.com/CxcXG2Bw

2017-05-06 07:11:14 -0500 commented question RDO TripleO QuickStart Undercloud failed

Here are the details: https://pastebin.com/ncjbbGZw

2017-05-05 09:53:17 -0500 asked a question RDO TripleO QuickStart Undercloud failed

Hello,

I'm trying to install TripleO QuickStart on CentOS 7 but it failed at the "Install the undercloud". The error is:

TASK [undercloud-deploy : Install the undercloud] ******************************
task path: /root/.quickstart/usr/local/share/ansible/roles/undercloud-deploy/tasks/install-undercloud.yml:15
Friday 05 May 2017  11:39:57 +0000 (0:00:07.869)       0:18:53.032 ************
fatal: [undercloud]: FAILED! => {"changed": true, "cmd": "set -o pipefail && /home/stack/undercloud-install.sh 2>&1 | awk '{ print strftime(\"%Y-%m-%d %H:%M:%S |\"), $0; fflush(); }' > /home/stack/undercloud_install.log", "delta": "0:44:49.399170", "end": "2017-05-05 12:24:51.173525", "failed": true, "rc": 1, "start": "2017-05-05 11:40:01.774355", "stderr": "", "stdout": "", "stdout_lines": [], "warnings": []}

PLAY RECAP *********************************************************************
163.172.168.222            : ok=110  changed=55   unreachable=0    failed=0
localhost                  : ok=18   changed=8    unreachable=0    failed=0
undercloud                 : ok=6    changed=5    unreachable=0    failed=1

Do you know what is going wrong ?

Thanks.

2017-03-14 12:40:51 -0500 received badge  Famous Question (source)
2016-11-05 12:24:35 -0500 commented question recipe for target '/build/bin/yumdownloader' failed- Fuel iso

I have the same issue. Did you manage to make it work ?

2016-10-01 08:56:07 -0500 received badge  Notable Question (source)
2016-09-13 14:30:43 -0500 received badge  Famous Question (source)
2016-07-24 01:13:34 -0500 received badge  Popular Question (source)
2016-05-09 01:27:37 -0500 received badge  Notable Question (source)
2016-05-08 14:08:02 -0500 asked a question Cinder LVM Volume local to Instance ?

Hi,

I have a setup where Compute and Cinder (using LVM) is on the same machine in a multi node environment (multiple Compute+Cinder LVM).

I would like to know if there is anyway to force a Cinder LVM volume to be on the same node as the instance ?

The goal would be to avoid using the network for the instance to use the volume.

Thanks,

Guillaume.

2016-05-07 04:12:40 -0500 received badge  Popular Question (source)
2016-05-06 18:16:37 -0500 received badge  Scholar (source)
2016-05-06 18:16:35 -0500 received badge  Supporter (source)
2016-05-06 16:28:29 -0500 asked a question Avoid routing every network trafic to Network Node

Hi,

As I understood how Openstack and network are working together. In a multi node environment, every network traffic from the nova instance is sent to the network node which decides where and how to forward it. Meaning that if my network node goes down my instances don't have access to the Internet and the network node is the bottleneck.

So my question is the following: if I have instances that does a lot of I/O to the public network (Internet) is there any way to avoid the instance network traffic to always go through the network node? I do not need to access instances from the Internet but I'd like the instance to access Internet without going through the network node.

Thank you.

2015-12-23 22:36:05 -0500 received badge  Famous Question (source)
2015-12-22 09:55:33 -0500 received badge  Notable Question (source)
2015-11-09 03:12:33 -0500 received badge  Popular Question (source)
2015-11-04 09:56:04 -0500 asked a question How to build trove images ?

Hello,

I can't figure out how to build trove images. What I did is clone the repos:

git clone https://git.openstack.org/openstack/diskimage-builder
git clone https://github.com/openstack/trove-integration.git
git clone https://github.com/openstack/tripleo-image-elements

Then, tried to create the image:

export REDSTACK_SCRIPTS=~/Documents/openstack/image-builder/trove-integration/scripts
export PATH_TRIPLEO_ELEMENTS=~/Documents/openstack/image-builder/tripleo-image-elements
export ELEMENTS_PATH=$REDSTACK_SCRIPTS/files/elements:$PATH_TRIPLEO_ELEMENTS/elements

disk-image-create -a amd64 -o ubuntu-mysql ubuntu vm heat-cfntools cloud-init-datasources ubuntu-guest ubuntu-mysql

But I always get HOST_USERNAME not set. Did I missed something ?

Thanks for your help.

2015-11-02 12:21:20 -0500 asked a question getting ssh-key very slow (cloud-init)

Hello,

I'm using OpenStack Liberty and the official CentOS 7 GenericCloud Image. it takes up to 3 minutes to get the SSH keys. What can be wrong ?

Here is my boot log:

CentOS Linux 7 (Core)
Kernel 3.10.0-229.14.1.el7.x86_64 on an x86_64

localhost login: cloud-init[772]: Cloud-init v. 0.7.5 running 'init' at Mon, 02 Nov 2015 12:19:55 +0000. Up 34.45 seconds.
cloud-init[772]: ci-info: ++++++++++++++++++++++++++Net device info+++++++++++++++++++++++++++
cloud-init[772]: ci-info: +--------+------+--------------+---------------+-------------------+
cloud-init[772]: ci-info: | Device |  Up  |   Address    |      Mask     |     Hw-Address    |
cloud-init[772]: ci-info: +--------+------+--------------+---------------+-------------------+
cloud-init[772]: ci-info: |  lo:   | True |  127.0.0.1   |   255.0.0.0   |         .         |
cloud-init[772]: ci-info: | eth0:  | True | 192.168.0.15 | 255.255.255.0 | fa:16:3e:9e:53:9f |
cloud-init[772]: ci-info: +--------+------+--------------+---------------+-------------------+
cloud-init[772]: ci-info: ++++++++++++++++++++++++++++++++++Route info+++++++++++++++++++++++++++++++++++
cloud-init[772]: ci-info: +-------+-----------------+-------------+-----------------+-----------+-------+
cloud-init[772]: ci-info: | Route |   Destination   |   Gateway   |     Genmask     | Interface | Flags |
cloud-init[772]: ci-info: +-------+-----------------+-------------+-----------------+-----------+-------+
cloud-init[772]: ci-info: |   0   |     0.0.0.0     | 192.168.0.1 |     0.0.0.0     |    eth0   |   UG  |
cloud-init[772]: ci-info: |   1   | 169.254.169.254 | 192.168.0.1 | 255.255.255.255 |    eth0   |  UGH  |
cloud-init[772]: ci-info: |   2   |   192.168.0.0   |   0.0.0.0   |  255.255.255.0  |    eth0   |   U   |
cloud-init[772]: ci-info: +-------+-----------------+-------------+-----------------+-----------+-------+
cloud-init[772]: 2015-11-02 12:22:21,711 - util.py[WARNING]: Failed fetching metadata from url http://169.254.169.254/latest/meta-data
cloud-init[10748]: Cloud-init v. 0.7.5 running 'modules:config' at Mon, 02 Nov 2015 12:22:22 +0000. Up 181.55 seconds.
cloud-init[10770]: Cloud-init v. 0.7.5 running 'modules:final' at Mon, 02 Nov 2015 12:22:22 +0000. Up 181.85 seconds.
ci-info: ++++++++++Authorized keys from /home/centos/.ssh/authorized_keys for user centos+++++++++++
ci-info: +---------+-------------------------------------------------+---------+-------------------+
ci-info: | Keytype |                Fingerprint (md5)                | Options |      Comment      |
ci-info: +---------+-------------------------------------------------+---------+-------------------+
ci-info: | ssh-rsa | 75:bd:b2:66:be:d2:78:76:3f:d3:e6:3b:00:6f:c4:35 |    -    | Generated-by-Nova |
ci-info: +---------+-------------------------------------------------+---------+-------------------+
ec2: 
ec2: #############################################################
ec2: -----BEGIN SSH HOST KEY FINGERPRINTS-----
ec2: 256 12:8c:ca:77:97:67:13:47:8c:3a:a4:fa:e7:46:08:6c   (ECDSA)
ec2: 256 fc:4c:32:33:d8:c9:96:5a:07:2b:ff:b2:76:5a:38:28   (ED25519)
ec2: 2048 0b:a5:68:5c:93:44:f4:4d:49:65:d3:f2:98:3b:d9:85   (RSA)
ec2: -----END SSH HOST KEY FINGERPRINTS-----
ec2: #############################################################
-----BEGIN SSH HOST KEY KEYS-----
ecdsa-sha2-nistp256 AAAAE2VjZHNhLXNoYTItbmlzdHAyNTYAAAAIbmlzdHAyNTYAAABBBEwhyeNIzEboIE1vZVcW9j4sqISl97eA9OomJY2pqaaIg79GuXSEX/DnYtmk+unUfyWwRI/J2wKi/1PJJsnHQbY= 
ssh-ed25519 AAAAC3NzaC1lZDI1NTE5AAAAIGwUZad06YiUQg92rX/kAKhuOu9o7T5+V7WD+EQp5PaC 
ssh-rsa AAAAB3NzaC1yc2EAAAADAQABAAABAQDEXt8sl9hDT4XiO59sg9iAXIp31zh2L3ZU3pNUbqjBiH9UtdzBOx6uSOe9ic2Hk+8hu6Nk6tJVPqeKcCEF8tESYHvJr7HNZWpA4MRy0P1kyEXj1HRov88uVpByyh9CdcN70xhPVuFzaHgveLfobDoglFTXu5ebB0+dA2F6TaO9KDa/X/P2EpGxE6APJMTDI6dk3k4Ep4KFYAaHIQV1Sf9+2TGPjDhxtYQ+ns4pqMQpsMx+i4EGRawhaIKkPLMoLbK56mEVq1DqsVuLkl1uzBqt3AKgGZp5kHMIEjWftXJWl9oRbX4ulvPd0Zm3mZiKNiVMahLGCK4RS1TqZnFp81OJ 
-----END SSH HOST KEY KEYS-----
cloud-init[10770]: Cloud-init v. 0.7.5 finished at Mon, 02 Nov 2015 12:22:22 +0000. Datasource DataSourceOpenStack [net,ver=2].  Up 181.94 seconds