You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@cloudstack.apache.org by Jonathan Gowar <jo...@whiteheat.org.uk> on 2014/04/02 16:38:56 UTC

Adding a host

Hi,

 I am building a new small CloudStack.  I have the Managment server and
DB together, and have a separate Storage server.  The UI is operational,
so some success.

I would now like to add a host.  I followed this guide
https://cloudstack.apache.org/docs/en-US/Apache_CloudStack/4.2.0/html/Installation_Guide/hypervisor-kvm-install-flow.html specifically the bit about networking:-

auto lo
iface lo inet loopback

# The primary network interface
auto eth0.100
iface eth0.100 inet static
    address 192.168.42.11
    netmask 255.255.255.240
    gateway 192.168.42.1
    dns-nameservers 8.8.8.8 8.8.4.4
    dns-domain lab.example.org

# Public network
auto cloudbr0
iface cloudbr0 inet manual
    bridge_ports eth0.200
    bridge_fd 5
    bridge_stp off
    bridge_maxwait 1

# Private network
auto cloudbr1
iface cloudbr1 inet manual
    bridge_ports eth0.300
    bridge_fd 5
    bridge_stp off
    bridge_maxwait 1

After doing this, and rebooting I lose connectivity.  This is because
eth0 is now tagged as suggested in the guide, but I don't think there is
vLAN tagging on the rest of the network.

What's the easy solution to this?

Is it documented how to vLAN correctly the rest of my installation?

Regards,
Jon


Re: [SOLVED] Adding a host

Posted by Jonathan Gowar <jo...@whiteheat.org.uk>.
Finally I have been able to add a host.  

This failed for 2 reasons, firstly I didn't edit libvirtd.conf
correctly; with mdns_adv = 1 , it should equal 0, this prevented
libvirtd from starting, and thus in turn cloudstack-agent.

Secondly, I don't know if there's a typo in the documentation, but I had
to use this network interface configuration; swapping eth0 and
cloudbr0's static and manual lines:-

# The primary network interface
auto eth0
iface eth0 inet manual

# Public network
auto cloudbr0
iface cloudbr0 inet static
    address 192.168.42.11
    netmask 255.255.255.240
    gateway 192.168.42.1
    dns-nameservers 8.8.8.8 8.8.4.4
    dns-domain lab.example.org`
    bridge_ports eth0
    bridge_fd 5
    bridge_stp off
    bridge_maxwait 1

# Private network
auto cloudbr1
iface cloudbr1 inet manual
    bridge_ports none
    bridge_fd 5
    bridge_stp off
    bridge_maxwait 1


Re: Adding a host

Posted by Jonathan Gowar <jo...@whiteheat.org.uk>.
I removed the vLAN and swapped eth0 with cloudbr0 before it would even
communicate.  Not sure if that's a typo in the documentation, or if I've
just kludged it through.

Now when I attempt to add the host I get this output from setup.log

DEBUG:root:execute:uname -r
DEBUG:root:execute:uname -m
DEBUG:root:execute:hostname -f
DEBUG:root:execute:kvm-ok
DEBUG:root:execute:service apparmor status
DEBUG:root:execute:apparmor_status |grep libvirt
DEBUG:root:Failed to execute:
DEBUG:root:execute:sudo /usr/sbin/service libvirt-bin status
DEBUG:root:execute:sudo /usr/sbin/service libvirt-bin stop
DEBUG:root:Failed to execute:stop: Unknown instance:
DEBUG:root:execute:sudo update-rc.d -f libvirt-bin remove
DEBUG:root:execute:sudo update-rc.d -f libvirt-bin defaults
DEBUG:root:execute:sudo /usr/sbin/service libvirt-bin status
DEBUG:root:execute:sudo /usr/sbin/service libvirt-bin start
DEBUG:root:execute:ufw allow 22
DEBUG:root:execute:ufw allow 1798
DEBUG:root:execute:ufw allow 16509
DEBUG:root:execute:ufw allow proto tcp from any to any port 5900:6100
DEBUG:root:execute:ufw allow proto tcp from any to any port 49152:49216
DEBUG:root:execute:sudo /usr/sbin/service ufw status
DEBUG:root:execute:sudo /usr/sbin/service ufw stop
DEBUG:root:execute:sudo /usr/sbin/service ufw status
DEBUG:root:execute:sudo /usr/sbin/service ufw start
DEBUG:root:execute:sudo /usr/sbin/service cloudstack-agent status
DEBUG:root:Failed to execute: * could not access PID file for
cloudstack-agent
DEBUG:root:execute:sudo /usr/sbin/service cloudstack-agent stop
DEBUG:root:execute:sleep 30
DEBUG:root:execute:sudo update-rc.d -f cloudstack-agent remove
DEBUG:root:execute:sudo update-rc.d -f cloudstack-agent defaults
DEBUG:root:execute:sudo /usr/sbin/service cloudstack-agent status
DEBUG:root:Failed to execute: * could not access PID file for
cloudstack-agent
DEBUG:root:execute:sudo /usr/sbin/service cloudstack-agent start

Any ideas what causes this, as I've scanned the internet to no avail.

Regards,
Jon

On Wed, 2014-04-02 at 15:38 +0100, Jonathan Gowar wrote:
> Hi,
> 
>  I am building a new small CloudStack.  I have the Managment server and
> DB together, and have a separate Storage server.  The UI is operational,
> so some success.
> 
> I would now like to add a host.  I followed this guide
> https://cloudstack.apache.org/docs/en-US/Apache_CloudStack/4.2.0/html/Installation_Guide/hypervisor-kvm-install-flow.html specifically the bit about networking:-
> 
> auto lo
> iface lo inet loopback
> 
> # The primary network interface
> auto eth0.100
> iface eth0.100 inet static
>     address 192.168.42.11
>     netmask 255.255.255.240
>     gateway 192.168.42.1
>     dns-nameservers 8.8.8.8 8.8.4.4
>     dns-domain lab.example.org
> 
> # Public network
> auto cloudbr0
> iface cloudbr0 inet manual
>     bridge_ports eth0.200
>     bridge_fd 5
>     bridge_stp off
>     bridge_maxwait 1
> 
> # Private network
> auto cloudbr1
> iface cloudbr1 inet manual
>     bridge_ports eth0.300
>     bridge_fd 5
>     bridge_stp off
>     bridge_maxwait 1
> 
> After doing this, and rebooting I lose connectivity.  This is because
> eth0 is now tagged as suggested in the guide, but I don't think there is
> vLAN tagging on the rest of the network.
> 
> What's the easy solution to this?
> 
> Is it documented how to vLAN correctly the rest of my installation?
> 
> Regards,
> Jon
>