date:20180209

[Openstack] Routing in connected VMs

2018-02-09 Thread Navdeep Uniyal

Dear all,


I am trying to create a network chain manually of VMs in openstack by entering 
the routing table entries in the machines. However, it doesn't seems to work.
The network between the VMs is VLAN network on top of provider network.

Scenario is like : A-->B-->C

I have enabled the IP forwarding on the node B but I am not able to ping from A 
to C. ICMP echo requests are not reaching C.
I am able to ping from B to A and B to C. Please if someone could help in this 
regard.


Best Regards,
Navdeep
___
Mailing list: http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack
Post to : openstack@lists.openstack.org
Unsubscribe : http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack

Re: [Openstack] [openstack][openstackweb] can not registe new user at openstack.org

2018-02-09 Thread Jimmy McArthur


Hi -

I'm sorry for the troubles you're having in registering as a Foundation 
Member. If you could email me directly (ji...@openstack.org), I'd be 
happy to help you with the issue and get your membership set up.


Thank you,
Jimmy


Begin forwarded message:

*From: *mailto:guoyongxh...@163.com>>
*Subject: **[Openstack] [openstack][openstackweb] can not registe new 
user at openstack.org *

*Date: *February 9, 2018 at 9:34:09 AM CST
*To: *"openstack" >


it always tips "Please confirm that you are not a robots". But there is 
no way to confirm.

___
Mailing list: http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack
Post to : openstack@lists.openstack.org 


Unsubscribe : http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack
___
Mailing list: http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack
Post to : openstack@lists.openstack.org
Unsubscribe : http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack

Re: [Openstack] Ocata Created Ports Strange Issue

2018-02-09 Thread Eugen Block


Hi,

my input on this is very limited, but I believe we had a similar issue  
in our Ocata cloud. My workaround was like yours, detach the assigned  
port, recreate it and attach it again. The only strange thing was,  
that when I wanted to delete the port, the CLI reported that the port  
didn't exist, it literally disappeared!
I didn't spend very much time to debug it because it has not happened  
since then. And if I remember correctly, it occured around our large  
migration, where we upgraded our Ceph backend to the latest version,  
upgraded the OS of all nodes and also the cloud from Mitaka to Ocata  
(via Newton), it could have been a side effect of that, at least that  
was my hope.


So as I said, this is not of big help, but I can confirm your  
observation, unfortunately without any pointers to the cause. If this  
happens again, I will definitely spend more time on debugging! ;-)


Regards,
Eugen


Zitat von Georgios Dimitrakakis :


Dear all,

I have a small Ocata installation (1x controller + 2x compute nodes)  
on which I have manually created 5 network ports and afterwards each  
one of these ports is assigned to a specific instance (4Linux VMs  
and 1Windows). All these instances are located on one physical  
hypervisor (compute node) while the controller is also the  
networking node.


The other day we had to do system maintenance and all hosts (compute  
and network/controller) were powered off but before that we  
gracefully shutoff all running VMs.


As soon as maintenance finished we powered on everything and I met  
the following strange issue... Instances with an attached port were  
trying for very long time to get an IP from the DHCP server but they  
all manage to get one eventually with the exception of the Windows  
VM on which I had to assign it statically. Restarting networking  
services on controller/network and/or compute node didn't make any  
difference. On the other hand all newly spawned instances didn't  
have any problem no matter on which compute node they were spawned  
and their only difference was that they were automatically getting  
ports assigned. All the above happened on Friday and today (Monday)  
people were complaining that the Linux VMs didn't have network  
connectivity (Windows was working...), so I don't know the exact  
time the issue occured. I have tried to access all VMs using the  
"self-service" network by spawning a new instance unfortunately  
without success. The instance was successfully spawned, it had  
network connectivity but couldn't reach any of the afforementioned  
VMs.


What I did finally and solved the problem was to detach interfaces,  
deleted ports, re-created new ports with same IP address etc. and  
re-attached them to the VMs. As soon as I did that networking  
connectivity was back to normal without even having to restart the  
VMs.


Unfortunately I couldn't find any helpful information regarding this  
in the logs and I am wondering has anyone seen or experienced  
something similar?


Best regards,

G.

___
Mailing list: http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack
Post to : openstack@lists.openstack.org
Unsubscribe : http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack




--
Eugen Block voice   : +49-40-559 51 75
NDE Netzdesign und -entwicklung AG  fax : +49-40-559 51 77
Postfach 61 03 15
D-22423 Hamburg e-mail  : ebl...@nde.ag

Vorsitzende des Aufsichtsrates: Angelika Mozdzen
  Sitz und Registergericht: Hamburg, HRB 90934
  Vorstand: Jens-U. Mozdzen
   USt-IdNr. DE 814 013 983


___
Mailing list: http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack
Post to : openstack@lists.openstack.org
Unsubscribe : http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack

[Openstack] [openstack][openstackweb] can not registe new user at openstack.org

2018-02-09 Thread guoyongxhzhf

it always tips "Please confirm that you are not a robots". But there is no way 
to confirm.___
Mailing list: http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack
Post to : openstack@lists.openstack.org
Unsubscribe : http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack

Re: [Openstack] diskimage-builder: prepare ubuntu 17.x images

2018-02-09 Thread Volodymyr Litovka


Hi Tony,

this patch works for me:

--- 
diskimage-builder/diskimage_builder/elements/ubuntu/root.d/10-cache-ubuntu-tarball.orig 
2018-02-09 12:20:02.117793234 +
+++ 
diskimage-builder/diskimage_builder/elements/ubuntu/root.d/10-cache-ubuntu-tarball 
2018-02-09 13:25:48.654868263 +

@@ -14,7 +14,9 @@

 DIB_CLOUD_IMAGES=${DIB_CLOUD_IMAGES:-http://cloud-images.ubuntu.com}
 DIB_RELEASE=${DIB_RELEASE:-trusty}
-BASE_IMAGE_FILE=${BASE_IMAGE_FILE:-$DIB_RELEASE-server-cloudimg-$ARCH-root.tar.gz}
+SUFFIX="-root"
+[[ $DIB_RELEASE =~ (artful|bionic) ]] && SUFFIX=""
+BASE_IMAGE_FILE=${BASE_IMAGE_FILE:-$DIB_RELEASE-server-cloudimg-${ARCH}${SUFFIX}.tar.gz}
 
SHA256SUMS=${SHA256SUMS:-https://${DIB_CLOUD_IMAGES##http?(s)://}/$DIB_RELEASE/current/SHA256SUMS}
 CACHED_FILE=$DIB_IMAGE_CACHE/$BASE_IMAGE_FILE
 CACHED_FILE_LOCK=$DIB_LOCKFILES/$BASE_IMAGE_FILE.lock
@@ -45,9 +47,25 @@
 fi
 popd
 fi
-    # Extract the base image (use --numeric-owner to avoid UID/GID 
mismatch between
-    # image tarball and host OS e.g. when building Ubuntu image on an 
openSUSE host)
-    sudo tar -C $TARGET_ROOT --numeric-owner -xzf 
$DIB_IMAGE_CACHE/$BASE_IMAGE_FILE

+    if [ -n "$SUFFIX" ]; then
+  # Extract the base image (use --numeric-owner to avoid UID/GID 
mismatch between
+  # image tarball and host OS e.g. when building Ubuntu image on an 
openSUSE host)
+  sudo tar -C $TARGET_ROOT --numeric-owner -xzf 
$DIB_IMAGE_CACHE/$BASE_IMAGE_FILE

+    else
+  # Unpack image to IDIR, mount it on MDIR, copy it to TARGET_ROOT
+  IDIR="/tmp/`head /dev/urandom | tr -dc A-Za-z0-9 | head -c 13 ; 
echo ''`"
+  MDIR="/tmp/`head /dev/urandom | tr -dc A-Za-z0-9 | head -c 13 ; 
echo ''`"

+  sudo mkdir $IDIR $MDIR
+  sudo tar -C $IDIR --numeric-owner -xzf 
$DIB_IMAGE_CACHE/$BASE_IMAGE_FILE
+  sudo mount -o loop -t auto 
$IDIR/$DIB_RELEASE-server-cloudimg-${ARCH}.img $MDIR

+  pushd $PWD 2>/dev/null
+  cd $MDIR
+  sudo tar c . | sudo tar x -C $TARGET_ROOT -k --numeric-owner 
2>/dev/null

+  popd
+  # Clean up
+  sudo umount $MDIR
+  sudo rm -rf $IDIR $MDIR
+    fi
 }

 (


On 2/9/18 1:03 PM, Volodymyr Litovka wrote:

Hi Tony,

On 2/9/18 6:01 AM, Tony Breeds wrote:

On Thu, Feb 08, 2018 at 10:53:14PM +0200, Volodymyr Litovka wrote:

Hi colleagues,

does anybody here know how to prepare Ubuntu Artful (17.10) image using
diskimage-builder?

diskimage-builder use the following naming style for download -
$DIB_RELEASE-server-cloudimg-$ARCH-root.tar.gz

and while "-root" names are there for trusty/amd64 and xenial/amd64 distros,
these archives for artful (and bionic) are absent on
cloud-images.ubuntu.com. There are just different kinds of images, not
source tree as in -root archives.

I will appreciate any ideas or knowledge how to customize 17.10-based image
using diskimage-builder or in diskimage-builder-like fashion.

You might like to investigate the ubuntu-minimal DIB element which will
build your ubuntu image from apt rather than starting with the pre-built
image.

good idea, but with

export DIST="ubuntu-minimal"
export DIB_RELEASE=artful

diskimage-builder fails with the following debug:

2018-02-09 10:33:22.426 | dib-run-parts Sourcing environment file 
/tmp/in_target.d/pre-install.d/../environment.d/10-dib-init-system.bash
2018-02-09 10:33:22.427 | + source 
/tmp/in_target.d/pre-install.d/../environment.d/10-dib-init-system.bash
2018-02-09 10:33:22.427 |  dirname 
/tmp/in_target.d/pre-install.d/../environment.d/10-dib-init-system.bash
2018-02-09 10:33:22.428 | +++ 
PATH='$PATH:/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/tmp/in_target.d/pre-install.d/../environment.d/..'

2018-02-09 10:33:22.428 | +++ dib-init-system
2018-02-09 10:33:22.429 | + set -eu
2018-02-09 10:33:22.429 | + set -o pipefail
2018-02-09 10:33:22.429 | + '[' -f /usr/bin/systemctl -o -f 
/bin/systemctl ']'

2018-02-09 10:33:22.429 | + [[ -f /sbin/initctl ]]
2018-02-09 10:33:22.429 | + [[ -f /etc/gentoo-release ]]
2018-02-09 10:33:22.429 | + [[ -f /sbin/init ]]
2018-02-09 10:33:22.429 | + echo 'Unknown init system'
2018-02-09 10:36:54.852 | + exit 1
2018-02-09 10:36:54.853 | ++ DIB_INIT_SYSTEM='Unknown init system

while earlier it find systemd

2018-02-09 10:33:22.221 | dib-run-parts Sourcing environment file 
/tmp/dib_build.fJUf6F4d/hooks/extra-data.d/../environment.d/10-dib-init-system.bash
2018-02-09 10:33:22.223 | + source 
/tmp/dib_build.fJUf6F4d/hooks/extra-data.d/../environment.d/10-dib-init-system.bash
2018-02-09 10:33:22.223 |  dirname 
/tmp/dib_build.fJUf6F4d/hooks/extra-data.d/../environment.d/10-dib-init-system.bash
2018-02-09 10:33:22.224 | +++ 
PATH=/home/doka/DIB/dib/bin:/home/doka/DIB/dib/bin:/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/snap/bin:/tmp/dib_build.fJUf6F4d/hooks/extra-data.d/../environment.d/..

2018-02-09 10:33:22.224 | +++ dib-init-system
2018-02-09 10:33:22.225 | + set -eu
2018-02-09 10:33:22.225 | + set -o pipefail
2018-

Re: [Openstack] diskimage-builder: prepare ubuntu 17.x images

2018-02-09 Thread Volodymyr Litovka


Hi Tony,

On 2/9/18 6:01 AM, Tony Breeds wrote:

On Thu, Feb 08, 2018 at 10:53:14PM +0200, Volodymyr Litovka wrote:

Hi colleagues,

does anybody here know how to prepare Ubuntu Artful (17.10) image using
diskimage-builder?

diskimage-builder use the following naming style for download -
$DIB_RELEASE-server-cloudimg-$ARCH-root.tar.gz

and while "-root" names are there for trusty/amd64 and xenial/amd64 distros,
these archives for artful (and bionic) are absent on
cloud-images.ubuntu.com. There are just different kinds of images, not
source tree as in -root archives.

I will appreciate any ideas or knowledge how to customize 17.10-based image
using diskimage-builder or in diskimage-builder-like fashion.

You might like to investigate the ubuntu-minimal DIB element which will
build your ubuntu image from apt rather than starting with the pre-built
image.

good idea, but with

export DIST="ubuntu-minimal"
export DIB_RELEASE=artful

diskimage-builder fails with the following debug:

2018-02-09 10:33:22.426 | dib-run-parts Sourcing environment file 
/tmp/in_target.d/pre-install.d/../environment.d/10-dib-init-system.bash
2018-02-09 10:33:22.427 | + source 
/tmp/in_target.d/pre-install.d/../environment.d/10-dib-init-system.bash
2018-02-09 10:33:22.427 |  dirname 
/tmp/in_target.d/pre-install.d/../environment.d/10-dib-init-system.bash
2018-02-09 10:33:22.428 | +++ 
PATH='$PATH:/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/tmp/in_target.d/pre-install.d/../environment.d/..'

2018-02-09 10:33:22.428 | +++ dib-init-system
2018-02-09 10:33:22.429 | + set -eu
2018-02-09 10:33:22.429 | + set -o pipefail
2018-02-09 10:33:22.429 | + '[' -f /usr/bin/systemctl -o -f 
/bin/systemctl ']'

2018-02-09 10:33:22.429 | + [[ -f /sbin/initctl ]]
2018-02-09 10:33:22.429 | + [[ -f /etc/gentoo-release ]]
2018-02-09 10:33:22.429 | + [[ -f /sbin/init ]]
2018-02-09 10:33:22.429 | + echo 'Unknown init system'
2018-02-09 10:36:54.852 | + exit 1
2018-02-09 10:36:54.853 | ++ DIB_INIT_SYSTEM='Unknown init system

while earlier it find systemd

2018-02-09 10:33:22.221 | dib-run-parts Sourcing environment file 
/tmp/dib_build.fJUf6F4d/hooks/extra-data.d/../environment.d/10-dib-init-system.bash
2018-02-09 10:33:22.223 | + source 
/tmp/dib_build.fJUf6F4d/hooks/extra-data.d/../environment.d/10-dib-init-system.bash
2018-02-09 10:33:22.223 |  dirname 
/tmp/dib_build.fJUf6F4d/hooks/extra-data.d/../environment.d/10-dib-init-system.bash
2018-02-09 10:33:22.224 | +++ 
PATH=/home/doka/DIB/dib/bin:/home/doka/DIB/dib/bin:/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/snap/bin:/tmp/dib_build.fJUf6F4d/hooks/extra-data.d/../environment.d/..

2018-02-09 10:33:22.224 | +++ dib-init-system
2018-02-09 10:33:22.225 | + set -eu
2018-02-09 10:33:22.225 | + set -o pipefail
2018-02-09 10:33:22.225 | + '[' -f /usr/bin/systemctl -o -f 
/bin/systemctl ']'

2018-02-09 10:33:22.225 | + echo systemd
2018-02-09 10:33:22.226 | ++ DIB_INIT_SYSTEM=systemd
2018-02-09 10:33:22.226 | ++ export DIB_INIT_SYSTEM

it seems somewhere in the middle something happens to systemd package

In the meantime I'll look at how we can consume the .img file, which is
similar to what we'd need to do for Fedora
script 
diskimage-builder/diskimage_builder/elements/ubuntu/root.d/10-cache-ubuntu-tarball 
contains the function get_ubuntu_tarball() which, after all checks, does 
the following:


sudo tar -C $TARGET_ROOT --numeric-owner -xzf 
$DIB_IMAGE_CACHE/$BASE_IMAGE_FILE


probably, the easiest hack around the issue is to change above to smth like

sudo (
mount -o loop  
tar cv   | tar xv -C $TARGET_ROOT ...
)

Will try this.

--
Volodymyr Litovka
  "Vision without Execution is Hallucination." -- Thomas Edison

___
Mailing list: http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack
Post to : openstack@lists.openstack.org
Unsubscribe : http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack

[Openstack] Routing in connected VMs

Re: [Openstack] [openstack][openstackweb] can not registe new user at openstack.org

Re: [Openstack] Ocata Created Ports Strange Issue

[Openstack] [openstack][openstackweb] can not registe new user at openstack.org

Re: [Openstack] diskimage-builder: prepare ubuntu 17.x images

Re: [Openstack] diskimage-builder: prepare ubuntu 17.x images

6 matches

Site Navigation

Mail list logo

Footer information