Re: [Rdo-list] I can't get access to VM instances
by Pasquale Salza
I have a question. If I want to add any public network, do I need to
statically assign every compute node to the same network on one of the
interfaces? I mean, in order to access to VMs which have the floating IP on
that network.
For example, having the VMs on 172.16.58.0/24 external network and compute
nodes with interfaces assigned with different networks.
Il 21/feb/2015 21:34 "Dan Sneddon" <dsneddon(a)redhat.com> ha scritto:
> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
>
> On 02/21/2015 12:14 AM, Pasquale Salza wrote:
> > Thank you! Yes you were right, I meant to chose 6 VMs and give them
> > 6 IPs. I forgot the router IP.
> >
> > Is there any problem in not giving direct internet access to
> > machines, but using IP forwarding on controller?
> >
> > Il 21/feb/2015 01:35 "Dan Sneddon" <dsneddon(a)redhat.com
> > <mailto:dsneddon@redhat.com>> ha scritto:
> >
> > On 02/20/2015 03:29 PM, Pasquale Salza wrote:
> >> Whops! I figured out just few seconds after I sent the mail! Ok,
> >> tomorrow I'll try with it. :) I'd like to share how I want to
> >> organise my network in order to get some advices.
> >
> >> Let's say I have 7 machines and 7 spare IPs on the network
> >> 172.16.58.0/24 <http://172.16.58.0/24> <http://172.16.58.0/24>
> > which are also associated to
> >> 7 public (internet) IPs.
> >
> >> I'd like to reserve 6 IPs for 6 VMs I could instanciate on
> >> OpenStack.
> >
> >> So I planned to do this: the controller node has a static IP on
> >> eth0 of the 7 in 172.16.58.50/24 <http://172.16.58.50/24>
> > <http://172.16.58.50/24> network
> >> so as I can access it from outside. I add an alias eth0:0 with
> >> which I connect the controller to the Management network of
> >> OpenStack, the 10.0.1.0/24 <http://10.0.1.0/24>
> > <http://10.0.1.0/24> network. Also on
> >> the controller, I set statically the IP for eth1 with one of
> >> float IPs network 192.168.0.0/16 <http://192.168.0.0/16>
> > <http://192.168.0.0/16> network. With
> >> iptables, I add the rule of forwarding everithing on eth0 and
> >> eth1, so the other nodes can get Internet access on network
> >> 10.0.1.0/24 <http://10.0.1.0/24> <http://10.0.1.0/24>.
> >
> >> On the compute nodes I set eth0 as one of IPs on 10.0.1.0/24
> > <http://10.0.1.0/24>
> >> <http://10.0.1.0/24> management network and eth1 as one on
> >> 192.168.0.0/16 <http://192.168.0.0/16> <http://192.168.0.0/16>.
> >
> >> Om each node I put the bridge on eth1.
> >
> >> With RDO I put virtualisation and tunneling only on eth1.
> >
> >> When the installatation has finished, I create a private neutron
> >> network 10.100.0.0/16 <http://10.100.0.0/16>
> > <http://10.100.0.0/16> and two public
> >> networks of floating IPs. The first is 192.168.0.0/24
> > <http://192.168.0.0/24>
> >> <http://192.168.0.0/24> for any kind of VM. The other is the
> >> 172.16.58.0/24 <http://172.16.58.0/24> <http://172.16.58.0/24>
> > network, limited to the 6
> >> available IPs with which I can put virtual machines on Internet.
> >
> >> Does it make sense or I'm doing some mistakes? Do you have any
> >> other idea?
> >
> >> Thank you very much indeed!
> >
> >> Pasquale
> >
> >> On 02/20/2015 02:07 PM, Pasquale Salza wrote:
> >>> Hi Rhys, I suppose so, because these are my iptables rules:
> >
> >>> iptables -F iptables -t nat -F iptables -P INPUT ACCEPT
> >>> iptables -P OUTPUT ACCEPT iptables -P FORWARD ACCEPT iptables
> >>> -A INPUT -d 172.16.58.0/24 <http://172.16.58.0/24>
> >>> <http://172.16.58.0/24>
> > <http://172.16.58.0/24>
> >>> -m
> >> state --state
> >>> ESTABLISHED,RELATED -j ACCEPT iptables -A INPUT -d
> >>> 172.16.58.0/24 <http://172.16.58.0/24>
> >> <http://172.16.58.0/24>
> >>> <http://172.16.58.0/24> -p tcp --dport ssh -j ACCEPT iptables
> >>> -A INPUT -d 172.16.58.0/24 <http://172.16.58.0/24>
> > <http://172.16.58.0/24>
> >> <http://172.16.58.0/24> -p tcp --dport www
> >>> -j ACCEPT iptables -A INPUT -d 172.16.58.0/24
> >>> <http://172.16.58.0/24> <http://172.16.58.0/24>
> >>> <http://172.16.58.0/24> -p tcp --dport pptp -j ACCEPT iptables
> >>> -A INPUT -d 172.16.58.0/24
> > <http://172.16.58.0/24>
> >>> <http://172.16.58.0/24>
> >> <http://172.16.58.0/24> -p tcp --sport
> >>> domain -j ACCEPT iptables -A INPUT -d 172.16.58.0/24
> > <http://172.16.58.0/24>
> >> <http://172.16.58.0/24>
> >>> <http://172.16.58.0/24> -p tcp --dport domain -j ACCEPT
> >>> iptables -A INPUT -d 172.16.58.0/24 <http://172.16.58.0/24>
> > <http://172.16.58.0/24>
> >> <http://172.16.58.0/24> -p udp --sport
> >>> domain -j ACCEPT iptables -A INPUT -d 172.16.58.0/24
> > <http://172.16.58.0/24>
> >> <http://172.16.58.0/24>
> >>> <http://172.16.58.0/24> -p udp --dport domain -j ACCEPT
> >>> iptables -A INPUT -d 172.16.58.0/24 <http://172.16.58.0/24>
> > <http://172.16.58.0/24>
> >> <http://172.16.58.0/24> -p gre -j ACCEPT
> >>> iptables -A INPUT -d 172.16.58.0/24 <http://172.16.58.0/24>
> > <http://172.16.58.0/24>
> >> <http://172.16.58.0/24> -p icmp
> >>> -j ACCEPT iptables -A INPUT -d 172.16.58.0/24
> >>> <http://172.16.58.0/24> <http://172.16.58.0/24>
> >>> <http://172.16.58.0/24> -j DROP iptables -t nat -A POSTROUTING
> >>> -o eth0 -j MASQUERADE service iptables save
> >
> >>> Firstly, do you think I planned the network organisation well?
> >>> Do you have other suggestion (best practices) with 2
> >>> interfaces?
> >
> >
> >>> 2015-02-20 18:30 GMT+01:00 Rhys Oxenham <roxenham(a)redhat.com
> > <mailto:roxenham@redhat.com>
> >> <mailto:roxenham@redhat.com <mailto:roxenham@redhat.com>>
> >>> <mailto:roxenham@redhat.com <mailto:roxenham@redhat.com>
> > <mailto:roxenham@redhat.com <mailto:roxenham@redhat.com>>>>:
> >
> >>> Hi Pasquale,
> >
> >>> Did you modify your security group rules to allow ICMP and/or
> >>> 22:tcp access?
> >
> >>> Many thanks Rhys
> >
> >>>> On 20 Feb 2015, at 17:11, Pasquale Salza
> >>>> <pasquale.salza(a)gmail.com <mailto:pasquale.salza@gmail.com>
> > <mailto:pasquale.salza@gmail.com
> > <mailto:pasquale.salza@gmail.com>>
> >>> <mailto:pasquale.salza@gmail.com
> >>> <mailto:pasquale.salza@gmail.com>
> >>> <mailto:pasquale.salza@gmail.com
> >>> <mailto:pasquale.salza@gmail.com>>>>
> >> wrote:
> >>>>
> >>>> Hi there, I have a lot of problems with RDO/OpenStack
> >>> configuration. Firstly, I need to describe my network
> >>> situation.
> >>>>
> >>>> I have 7 machine, each of them with 2 NIC. I would like to
> >>>> use one
> >>> machine as a controller/network node and the others as compute
> >>> nodes.
> >>>>
> >>>> I would like to use the eth0 to connect nodes to internet
> >>>> (and get
> >>> access by remote sessions) with the network "172.16.58.0/24
> > <http://172.16.58.0/24>
> >> <http://172.16.58.0/24>
> >>> <http://172.16.58.0/24>", in which I have just 7 available
> >>> IPs, and eth1 as configuration network on the network
> >>> 10.42.100.0/42
> > <http://10.42.100.0/42>
> >> <http://10.42.100.0/42>
> >>> <http://10.42.100.0/42>.
> >>>>
> >>>> This is my current configuration, for each node (varying the
> >>>> IPs
> >>> on each machine):
> >>>>
> >>>> eth0: DEVICE=eth0 TYPE=Ethernet ONBOOT=yes BOOTPROTO=static
> >>>> IPADDR=172.16.58.50 NETMASK=255.255.255.0
> >>>> GATEWAY=172.16.58.254 DNS1=172.16.58.50 DOMAIN=###
> >>>> DEFROUTE="yes"
> >>>>
> >>>> eth1: DEVICE=eth1 TYPE=OVSPort DEVICETYPE=ovs
> >>>> OVS_BRIDGE=br-ex ONBOOT=yes
> >>>>
> >>>> br-ex: DEVICE=br-ex DEVICETYPE=ovs TYPE=OVSBridge
> >>>> BOOTPROTO=static IPADDR=10.42.100.1 NETMASK=255.255.255.0
> >>>> ONBOOT=yes
> >>>>
> >>>> I'd like to have instances on 10.42.200.0/24
> >>>> <http://10.42.200.0/24> <http://10.42.200.0/24>
> >>> <http://10.42.200.0/24> virtual private network and the
> >>> remaining IPs of 10.42.100.0/24 <http://10.42.100.0/24>
> > <http://10.42.100.0/24>
> >>> <http://10.42.100.0/24>
> >> network as floating
> >>> IPs.
> >>>>
> >>>> These are the relevant parts of my answers.txt file:
> >>>>
> >>>> CONFIG_CONTROLLER_HOST=10.42.100.1
> >>>>
> >
> >
> >
> CONFIG_COMPUTE_HOSTS=10.42.100.10,10.42.100.11,10.42.100.12,10.42.100.13,10.42.100.14,10.42.100.15
> >
> >
> >
> >>> CONFIG_NETWORK_HOSTS=10.42.100.1
> >>>> CONFIG_AMQP_HOST=10.42.100.1 CONFIG_MARIADB_HOST=10.42.100.1
> >>>> CONFIG_NOVA_COMPUTE_PRIVIF=eth1
> >>>> CONFIG_NOVA_NETWORK_PUBIF=eth1
> >>>> CONFIG_NOVA_NETWORK_PRIVIF=eth1
> >>>> CONFIG_NOVA_NETWORK_FIXEDRANGE=10.42.200.0/24
> > <http://10.42.200.0/24>
> >>>> <http://10.42.200.0/24>
> >>> <http://10.42.200.0/24>
> >>>> CONFIG_NOVA_NETWORK_FLOATRANGE=10.42.100.0/24
> > <http://10.42.100.0/24>
> >>>> <http://10.42.100.0/24>
> >>> <http://10.42.100.0/24>
> >>>> CONFIG_NEUTRON_L3_EXT_BRIDGE=br-ex
> >>>> CONFIG_NEUTRON_ML2_TYPE_DRIVERS=vxlan
> >>>> CONFIG_NEUTRON_ML2_TENANT_NETWORK_TYPES=vxlan
> >>>> CONFIG_NEUTRON_ML2_VNI_RANGES=10:100
> >>>> CONFIG_NEUTRON_LB_INTERFACE_MAPPINGS=
> >>>> CONFIG_NEUTRON_OVS_BRIDGE_MAPPINGS=
> >>>> CONFIG_NEUTRON_OVS_BRIDGE_IFACES=
> >>>> CONFIG_NEUTRON_OVS_TUNNEL_IF=eth1
> >>>>
> >>>> After the installation, I configure the network like this:
> >>>>
> >>>> neutron router-create router neutron net-create private
> >>>> neutron subnet-create private 10.42.200.0/24
> >>>> <http://10.42.200.0/24> <http://10.42.200.0/24>
> >>> <http://10.42.200.0/24> --name private-subnet
> >>>> neutron router-interface-add router private-subnet neutron
> >>>> net-create public --router:external=True neutron
> >>>> subnet-create public 10.42.100.0/24 <http://10.42.100.0/24>
> > <http://10.42.100.0/24>
> >>> <http://10.42.100.0/24> --name public-subnet
> >>> --enable_dhcp=False --allocation-pool
> >>> start=10.42.100.100,end=10.42.100.200 --no-gateway
> >>>> neutron router-gateway-set router public
> >>>>
> >>>> I'm able to launch instances but I can't get access
> >>>> (ping/ssh) to
> >>> them.
> >>>>
> >>>> I don't know if I'm doing something wrong starting from
> >>>> planning.
> >>>>
> >>>> Please, help me!
> >>>>
> >>>> _______________________________________________ Rdo-list
> >>>> mailing list Rdo-list(a)redhat.com
> >>>> <mailto:Rdo-list@redhat.com>
> > <mailto:Rdo-list@redhat.com <mailto:Rdo-list@redhat.com>>
> >> <mailto:Rdo-list@redhat.com <mailto:Rdo-list@redhat.com>
> > <mailto:Rdo-list@redhat.com <mailto:Rdo-list@redhat.com>>>
> >>>> https://www.redhat.com/mailman/listinfo/rdo-list
> >>>>
> >>>> To unsubscribe: rdo-list-unsubscribe(a)redhat.com
> > <mailto:rdo-list-unsubscribe@redhat.com>
> >> <mailto:rdo-list-unsubscribe@redhat.com
> > <mailto:rdo-list-unsubscribe@redhat.com>>
> >>> <mailto:rdo-list-unsubscribe@redhat.com
> > <mailto:rdo-list-unsubscribe@redhat.com>
> >> <mailto:rdo-list-unsubscribe@redhat.com
> > <mailto:rdo-list-unsubscribe@redhat.com>>>
> >
> >
> >
> >
> >>> -- Pasquale Salza
> >
> >>> e-mail: pasquale.salza(a)gmail.com
> >>> <mailto:pasquale.salza@gmail.com>
> >>> <mailto:pasquale.salza@gmail.com
> >>> <mailto:pasquale.salza@gmail.com>>
> >> <mailto:pasquale.salza@gmail.com
> >> <mailto:pasquale.salza@gmail.com>
> >> <mailto:pasquale.salza@gmail.com
> >> <mailto:pasquale.salza@gmail.com>>>
> >>> phone: +39 393 4415978 <tel:%2B39%20393%204415978>
> > <tel:%2B39%20393%204415978> fax: +39 089
> >> 8422939 <tel:%2B39%20089%208422939> skype: pasquale.salza
> >>> linkedin: http://it.linkedin.com/in/psalza/
> >
> >
> >>> _______________________________________________ Rdo-list
> >>> mailing list Rdo-list(a)redhat.com <mailto:Rdo-list@redhat.com>
> > <mailto:Rdo-list@redhat.com <mailto:Rdo-list@redhat.com>>
> >>> https://www.redhat.com/mailman/listinfo/rdo-list
> >
> >>> To unsubscribe: rdo-list-unsubscribe(a)redhat.com
> > <mailto:rdo-list-unsubscribe@redhat.com>
> >> <mailto:rdo-list-unsubscribe@redhat.com
> > <mailto:rdo-list-unsubscribe@redhat.com>>
> >
> >
> >> Those look like the iptables rule on the hypervisor. Rhys is
> >> talking about the Neutron security group rules. By default, ssh
> >> into VMs is not allowed. You need to permit ICMP and SSH in the
> >> security rules on the neutron network.
> >
> >> I don't see anything wrong with your network architecture at
> >> first glance, but floating IPs can be tricky at first. Start with
> >> basic VM-to-VM connectivity and add on from there.
> >
> >> Good luck!
> >
> >
> >> _______________________________________________ Rdo-list mailing
> >> list Rdo-list(a)redhat.com <mailto:Rdo-list@redhat.com>
> > <mailto:Rdo-list@redhat.com <mailto:Rdo-list@redhat.com>>
> >> https://www.redhat.com/mailman/listinfo/rdo-list
> >
> >> To unsubscribe: rdo-list-unsubscribe(a)redhat.com
> > <mailto:rdo-list-unsubscribe@redhat.com>
> >> <mailto:rdo-list-unsubscribe@redhat.com
> > <mailto:rdo-list-unsubscribe@redhat.com>>
> >
> > That sounds like it should work, but one of those 6 IP addresses
> > will need to be used for the Neutron router (that IP will be used
> > for SNAT for VMs that have no floating IP).
> >
> > I'm not sure what you mean when you say "I'd like to reserve 6 IPs
> > for 6 VMs I could instanciate on OpenStack." You can instantiate
> > more than one VM on each compute node, and if you have 6 compute
> > nodes then depending on size you could have dozens of VMs. Maybe
> > you just mean you could instantiate 6 VMs with public IPs?
> > Actually, due to the router IP, you would be limited to 5.
> >
> > Make sure you add the floating IP network as an external net.
> > Since your router will not be taking the .1 address, you will need
> > to create the port by hand with the chosen IP and add it to the
> > router.
> >
> > $ neutron net-create externalnet -- --router:external=True $
> > neutron subnet-create externalnet 172.16.58.0/24
> > <http://172.16.58.0/24> --name external \ --enable_dhcp=False
> > --allocation_pool start=172.16.58.x,\ end=172.16.58.x --gateway
> > 172.16.58.x (use your network gateway here - change the IP
> > addresses in the allocation range to match what is available on
> > your network) $ neutron router-create extrouter (name of your
> > router) $ neutron port-create externalnet --fixed-ip 172.16.58.x
> > (use desired router IP) $ neutron router-interface-add extrouter
> > port=$portid (port id from previous command) $ neutron
> > router-interface-add extrouter subnet=public (replace public with
> > the name of the 192.168.0.0/24 <http://192.168.0.0/24> network)
> >
> > Once that is done, you should be able to assign a floating IP to
> > any VM that has an interface on the 192.168.0.0/24
> > <http://192.168.0.0/24> network.
> >
> > P.S. - Several times in your email you mentioned 192.168.0.0/16
> > <http://192.168.0.0/16>, but that's not a valid network. I assume
> > you mean 192.168.0.0/24 <http://192.168.0.0/24>.
> >
> >
>
> That depends what you are trying to do. There are plenty of reasons
> why it might not work at first. You may need to troubleshoot.
>
> One issue that might come up is that you will be doing multiple levels
> of NAT. Some protocols won't work with multiple layers of translation.
>
> If your goal is to eventually make these VMs reachable from the
> Internet, there are a lot of factors in play above the OpenStack cloud.
>
> - --
> Dan Sneddon | Principal OpenStack Engineer
> dsneddon(a)redhat.com | redhat.com/openstack
> 650.254.4025 | @dxs on twitter
> -----BEGIN PGP SIGNATURE-----
> Version: GnuPG v1
>
> iQEcBAEBAgAGBQJU6OvEAAoJEFkV3ypsGNbjPyAH/1IAaeow2xMa5jn3Qm5x1OvZ
> o1trjIuR3VoYCwGYhM8s6lv1spAq44xFEG/bBjX6FDQlTgbpUFWeJupS6DeTyx9J
> k3k7MCtnM0hcEsoOfYoq3J/rRXhPk/fvYKHpknbA89xsby91qq9aLoEUdAABFzEJ
> 5Z3sa2mvf3D68VP9XBicRdi+ZWmsO+LF25kdpNxmZncanShj+EFkyJbkUgZOCfkR
> YiXswP4khAL91afY2VXkzVYG9DgRqmZGMq7SFXOVPsKZ4VnBwbZwduVQJFrVBGzg
> FSTIKE+kMucPB3VRetezY0tqI+g/PMkZk+/4pDM8EGM4RfjHGCZhKSrlZ5h/1H4=
> =BElH
> -----END PGP SIGNATURE-----
>
9 years, 9 months
Re: [Rdo-list] Rdo-list Digest, Vol 23, Issue 4
by Andrew Beekhof
> On 6 Feb 2015, at 3:48 am, Lars Kellogg-Stedman <lars(a)redhat.com> wrote:
>
> On Thu, Feb 05, 2015 at 10:42:18AM -0500, Andrew Beekhof wrote:
>> Perhaps it should though.
>
> Possibly! But that is a different question, and not one I can answer
> :). I do like having a convenient CLI-based installation tool; it makes
> testing much faster than having to roll out a web-based deployment
> tool.
Exactly. The easier it is to install, the more it will get tested.
If anyone is interested in working on this, I have some thoughts on how to achieve it but so far have lacked the free cycles to make any progress.
9 years, 9 months
[Rdo-list] High Availability configuration
by Alon Dotan
Dear All,
Someone managed to configure High Availability?
My setup contains 2 CentOS 7 controllers and about 15 compute nodes,
I want to configure High Availability between the controllers only
Thanks,
9 years, 9 months
[Rdo-list] Unable to SSH to instance
by Vedsar Kushwaha
I'm trying to connect openstack instance from last couple of weeks, but
still not successful.
I tried following link:
https://openstack.redhat.com/Neutron_with_existing_external_network
https://ask.openstack.org/en/question/52698/connecting-to-existing-networ...
Here is my configuration:
ifconfig:
br-ex: flags=4163<UP,BROADCAST,RUNNING,MULTICAST> mtu 1500
inet 10.16.37.221 netmask 255.255.255.0 broadcast 10.16.37.255
inet6 fe80::58dc:cdff:fe3c:624a prefixlen 64 scopeid 0x20<link>
ether b0:83:fe:75:95:9c txqueuelen 0 (Ethernet)
RX packets 11160 bytes 18527350 (17.6 MiB)
RX errors 0 dropped 0 overruns 0 frame 0
TX packets 9751 bytes 1061798 (1.0 MiB)
TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0
br-int: flags=4163<UP,BROADCAST,RUNNING,MULTICAST> mtu 1500
inet6 fe80::c071:edff:fe04:de44 prefixlen 64 scopeid 0x20<link>
ether c2:71:ed:04:de:44 txqueuelen 0 (Ethernet)
RX packets 42 bytes 4328 (4.2 KiB)
RX errors 0 dropped 0 overruns 0 frame 0
TX packets 8 bytes 648 (648.0 B)
TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0
lo: flags=73<UP,LOOPBACK,RUNNING> mtu 65536
inet 127.0.0.1 netmask 255.0.0.0
inet6 ::1 prefixlen 128 scopeid 0x10<host>
loop txqueuelen 0 (Local Loopback)
RX packets 504005 bytes 108257311 (103.2 MiB)
RX errors 0 dropped 0 overruns 0 frame 0
TX packets 504005 bytes 108257311 (103.2 MiB)
TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0
p2p1: flags=4163<UP,BROADCAST,RUNNING,MULTICAST> mtu 1500
inet6 fe80::b283:feff:fe75:959c prefixlen 64 scopeid 0x20<link>
ether b0:83:fe:75:95:9c txqueuelen 1000 (Ethernet)
RX packets 356442 bytes 372192516 (354.9 MiB)
RX errors 0 dropped 0 overruns 0 frame 0
TX packets 157458 bytes 12175539 (11.6 MiB)
TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0
nova secgroup-list-rules default:
+-------------+-----------+---------+-----------+--------------+
| IP Protocol | From Port | To Port | IP Range | Source Group |
+-------------+-----------+---------+-----------+--------------+
| tcp | 22 | 22 | 0.0.0.0/0 | |
| icmp | -1 | -1 | 0.0.0.0/0 | |
| | | | | default |
| | | | | default |
+-------------+-----------+---------+-----------+--------------+
sudo ovs-vsctl show:
077937f9-cf9d-40ca-af2b-f435153595d5
Bridge br-int
fail_mode: secure
Port patch-tun
Interface patch-tun
type: patch
options: {peer=patch-int}
Port br-int
Interface br-int
type: internal
Bridge br-ex
Port "p2p1"
Interface "p2p1"
Port br-ex
Interface br-ex
type: internal
Bridge br-tun
Port patch-int
Interface patch-int
type: patch
options: {peer=patch-tun}
Port br-tun
Interface br-tun
type: internal
ovs_version: "2.1.3"
Please help..
--
Vedsar Kushwaha
M.Tech-Computational Science
Indian Institute of Science
9 years, 9 months
[Rdo-list] staypuft - unable to install on centos6
by Mohammed Arafa
so i am experimenting with staypuft trying to learn how to install it
i have set up a VM with the latest centos6 and then added the foreman
repository and installed the staypuft-installer
it then fails but doesnt give me an error output - there is nothing in the
logs. whatsoever i have are my inputs. pls advise on how to get staypuft
installed
yum -y install
http://yum.theforeman.org/releases/latest/el6/x86_64/foreman-release.rpm
yum -y install foreman-installer-staypuft
staypuft-installer --foreman-plugin-discovery-install-images=true
ifconfig #confirm ip
vi /etc/hosts #make an entry for this host
hostname -f #verify
staypuft-installer --foreman-plugin-discovery-install-images=true
cat /var/log/foreman-installer/foreman-installer.log |grep -i error
___
[root@staypuft ~]# hostname -f
staypuft.marafa.vm
[root@staypuft ~]# staypuft-installer
--foreman-plugin-discovery-install-images=true
Networking setup:
Network interface: 'eth0'
IP address: '10.0.1.2'
Network mask: '255.255.255.0'
Network address: '10.0.1.0'
Host Gateway: '10.0.1.1'
DHCP range start: '10.0.1.3'
DHCP range end: '10.0.1.254'
DHCP Gateway: '10.0.1.2'
DNS forwarder: '8.8.8.7'
Domain: 'marafa.vm'
Foreman URL: 'https://staypuft.marafa.vm'
NTP sync host: '1.centos.pool.ntp.org'
Timezone: 'UTC'
Configure networking on this machine: ✓
Configure firewall on this machine: ✓
The installer can configure the networking and firewall rules on this
machine with the above configuration. Default values are populated from the
this machine's existing networking configuration.
If you DO NOT want to configure networking please set 'Configure networking
on this machine' to No before proceeding. Do this by selecting option 'Do
not configure networking' from the list below.
How would you like to proceed?:
1. Proceed with the above values
2. Change Network interface
3. Change IP address
4. Change Network mask
5. Change Network address
6. Change Host Gateway
7. Change DHCP range start
8. Change DHCP range end
9. Change DHCP Gateway
10. Change DNS forwarder
11. Change Domain
12. Change Foreman URL
13. Change NTP sync host
14. Change Timezone
15. Do not configure networking
16. Do not configure firewall
17. Cancel Installation
1
Configure client authentication
SSH public key: ''
Root password: '*******************************************'
Please set a default root password for newly provisioned machines. If you
choose not to set a password, it will be generated randomly. The password
must be a minimum of 8 characters. You can also set a public ssh key which
will be deployed to newly provisioned machines.
How would you like to proceed?:
1. Proceed with the above values
2. Change SSH public key
3. Change Root password
4. Toggle Root password visibility
3
new value for root password
********
enter new root password again to confirm
********
Configure client authentication
SSH public key: ''
Root password: '********'
Please set a default root password for newly provisioned machines. If you
choose not to set a password, it will be generated randomly. The password
must be a minimum of 8 characters. You can also set a public ssh key which
will be deployed to newly provisioned machines.
How would you like to proceed?:
1. Proceed with the above values
2. Change SSH public key
3. Change Root password
4. Toggle Root password visibility
4
Configure client authentication
SSH public key: ''
Root password: 'password'
Please set a default root password for newly provisioned machines. If you
choose not to set a password, it will be generated randomly. The password
must be a minimum of 8 characters. You can also set a public ssh key which
will be deployed to newly provisioned machines.
How would you like to proceed?:
1. Proceed with the above values
2. Change SSH public key
3. Change Root password
4. Toggle Root password visibility
1
Starting networking setup
Networking setup has finished
Preparing installation Done
Not running provisioning configuration since installation encountered
errors, exit code was 1
Something went wrong! Check the log for ERROR-level output
* Foreman is running at https://staypuft.marafa.vm
Initial credentials are admin / ZZVBfQ3WLAwnpHJH
* Foreman Proxy is running at https://staypuft.marafa.vm:8443
* Puppetmaster is running at port 8140
The full log is at /var/log/foreman-installer/foreman-installer.log
Something went wrong! Check the log for ERROR-level output
The full log is at /var/log/foreman-installer/foreman-installer.log
[root@staypuft ~]# cat /var/log/foreman-installer/foreman-installer.log
|grep -i error
[root@staypuft ~]#
--
<https://candidate.peoplecert.org/ReportsLink.aspx?argType=1&id=13D642E995...>
*805010942448935*
<https://www.redhat.com/wapps/training/certification/verify.html?certNumbe...>
*GR750055912MA*
<https://candidate.peoplecert.org/ReportsLink.aspx?argType=1&id=13D642E995...>
*Link to me on LinkedIn <http://www.linkedin.com/in/mohammedarafa>*
9 years, 9 months
[Rdo-list] I can't get access to VM instances
by Pasquale Salza
Hi there, I have a lot of problems with RDO/OpenStack configuration.
Firstly, I need to describe my network situation.
I have 7 machine, each of them with 2 NIC. I would like to use one machine
as a controller/network node and the others as compute nodes.
I would like to use the eth0 to connect nodes to internet (and get access
by remote sessions) with the network "172.16.58.0/24", in which I have just
7 available IPs, and eth1 as configuration network on the network
10.42.100.0/42.
This is my current configuration, for each node (varying the IPs on each
machine):
eth0:
DEVICE=eth0
TYPE=Ethernet
ONBOOT=yes
BOOTPROTO=static
IPADDR=172.16.58.50
NETMASK=255.255.255.0
GATEWAY=172.16.58.254
DNS1=172.16.58.50
DOMAIN=###
DEFROUTE="yes"
eth1:
DEVICE=eth1
TYPE=OVSPort
DEVICETYPE=ovs
OVS_BRIDGE=br-ex
ONBOOT=yes
br-ex:
DEVICE=br-ex
DEVICETYPE=ovs
TYPE=OVSBridge
BOOTPROTO=static
IPADDR=10.42.100.1
NETMASK=255.255.255.0
ONBOOT=yes
I'd like to have instances on 10.42.200.0/24 virtual private network and
the remaining IPs of 10.42.100.0/24 network as floating IPs.
These are the relevant parts of my answers.txt file:
CONFIG_CONTROLLER_HOST=10.42.100.1
CONFIG_COMPUTE_HOSTS=10.42.100.10,10.42.100.11,10.42.100.12,10.42.100.13,10.42.100.14,10.42.100.15
CONFIG_NETWORK_HOSTS=10.42.100.1
CONFIG_AMQP_HOST=10.42.100.1
CONFIG_MARIADB_HOST=10.42.100.1
CONFIG_NOVA_COMPUTE_PRIVIF=eth1
CONFIG_NOVA_NETWORK_PUBIF=eth1
CONFIG_NOVA_NETWORK_PRIVIF=eth1
CONFIG_NOVA_NETWORK_FIXEDRANGE=10.42.200.0/24
CONFIG_NOVA_NETWORK_FLOATRANGE=10.42.100.0/24
CONFIG_NEUTRON_L3_EXT_BRIDGE=br-ex
CONFIG_NEUTRON_ML2_TYPE_DRIVERS=vxlan
CONFIG_NEUTRON_ML2_TENANT_NETWORK_TYPES=vxlan
CONFIG_NEUTRON_ML2_VNI_RANGES=10:100
CONFIG_NEUTRON_LB_INTERFACE_MAPPINGS=
CONFIG_NEUTRON_OVS_BRIDGE_MAPPINGS=
CONFIG_NEUTRON_OVS_BRIDGE_IFACES=
CONFIG_NEUTRON_OVS_TUNNEL_IF=eth1
After the installation, I configure the network like this:
neutron router-create router
neutron net-create private
neutron subnet-create private 10.42.200.0/24 --name private-subnet
neutron router-interface-add router private-subnet
neutron net-create public --router:external=True
neutron subnet-create public 10.42.100.0/24 --name public-subnet
--enable_dhcp=False --allocation-pool start=10.42.100.100,end=10.42.100.200
--no-gateway
neutron router-gateway-set router public
I'm able to launch instances but I can't get access (ping/ssh) to them.
I don't know if I'm doing something wrong starting from planning.
Please, help me!
9 years, 9 months
