[ovirt-users] root login using HE w/o cloud-init?

2016-12-18 Thread Mark Steckel
Still trying to get a single server hosted engine setup running at Hetzner.de...

If I use the HE Appliance and do not use cloud-init the VM launches but can not 
be accessed.


[ INFO  ] Detecting available oVirt engine appliances
  The following appliance have been found on your system:
[1] - The oVirt Engine Appliance image (OVA) - 
4.0-20161210.1.el7.centos
[2] - Directly select an OVA file
  Please select an appliance (1, 2) [1]: 1
[ INFO  ] Verifying its sha1sum
[ INFO  ] Checking OVF archive content (could take a few minutes depending on 
archive size)
[ INFO  ] Checking OVF XML content (could take a few minutes depending on 
archive size)
[WARNING] OVF does not contain a valid image description, using default.
  Would you like to use cloud-init to customize the appliance on the 
first boot (Yes, No)[Yes]? No
[WARNING] The oVirt engine appliance is not configured with a default password, 
please consider configuring it via cloud-init



  Make a selection from the options below:
  (1) Continue setup - oVirt-Engine installation is ready and 
ovirt-engine service is up
  (2) Abort setup
  (3) Power off and restart the VM
  (4) Destroy VM and abort setup



At this point I can access the VM via vnc but am unable to login.

Is root login possible in this situation?



___
Users mailing list
Users@ovirt.org
http://lists.ovirt.org/mailman/listinfo/users


Re: [ovirt-users] Single server hosted engine... almost there

2016-12-08 Thread Mark Steckel
Hi,

- Derek Atkins <de...@ihtfp.com> wrote:
> Hi,
> 
> On Thu, December 8, 2016 11:15 am, Mark Steckel wrote:
> >
> > - Derek Atkins <de...@ihtfp.com> wrote:
> >> Hi,
> >>
> >> Mark Steckel <m...@fix.net> writes:
> >>
> >> > Am I missing and or just misunderstanding something here?
> >> >
> >> > Oh, and does ip_forwarding need to be set in the kernel? (ie
> >> > net.ipv4.ip_forward=1)
> >>
> >> If you expect the host to act as the router for your /29, then yes, it
> >> would need to forward packets.  You will also need to set up the
> >> firewall on the host to properly forward packets through.
> >>
> >> It honestly might be easier for you to get an actual router instead of
> >> trying to force your host to act as both host+router.  I suspect the
> >> hosted-engine --deploy script wouldn't really know how to properly
> >> handle the host as a router so it might either break that configuration
> >> or at least not know how to set it up.
> >
> > Agreed. Unfortunately, the hosting company (Hetzner) providing the server
> > requires the /29 to be on the host.
> >
> > Googling "ovirt Hetzner" shows that a number of people have attempted this
> > at Hetzner and have run into various problems. Here is one of the more
> > relevant examples:
> >
> > http://lists.ovirt.org/pipermail/users/2014-January/019785.html
> > (check out the first link)
> > http://lists.ovirt.org/pipermail/users/2014-February/020913.html
> >
> > So it seems this is doable, but needs a bit more finesse than I've used so
> > far.
> 
> Yeah, I suspect you will need to set up your engine NOT using the
> appliance, but instead install CentOS and then the engine inside the VM. 
> This will give you more direct access to the engine VM, and should give
> you the opportunity to set up the bridge routing during the process.

Makes sense, at least in concept. 

But are you suggesting that I manually set up the vm for the engine (ie not use 
"hosted-engine --deploy") and then manually run engine setup from w/i the vm?



> 
> > Mark
> 
> -derek
> 
> -- 
>Derek Atkins 617-623-3745
>de...@ihtfp.com www.ihtfp.com
>Computer and Internet Security Consultant
> 

___
Users mailing list
Users@ovirt.org
http://lists.phx.ovirt.org/mailman/listinfo/users


Re: [ovirt-users] Single server hosted engine... almost there

2016-12-08 Thread Mark Steckel

- Derek Atkins <de...@ihtfp.com> wrote:
> Hi,
> 
> Mark Steckel <m...@fix.net> writes:
> 
> > Am I missing and or just misunderstanding something here?
> >
> > Oh, and does ip_forwarding need to be set in the kernel? (ie
> > net.ipv4.ip_forward=1)
> 
> If you expect the host to act as the router for your /29, then yes, it
> would need to forward packets.  You will also need to set up the
> firewall on the host to properly forward packets through.
> 
> It honestly might be easier for you to get an actual router instead of
> trying to force your host to act as both host+router.  I suspect the
> hosted-engine --deploy script wouldn't really know how to properly
> handle the host as a router so it might either break that configuration
> or at least not know how to set it up.

Agreed. Unfortunately, the hosting company (Hetzner) providing the server 
requires the /29 to be on the host.

Googling "ovirt Hetzner" shows that a number of people have attempted this at 
Hetzner and have run into various problems. Here is one of the more relevant 
examples:

http://lists.ovirt.org/pipermail/users/2014-January/019785.html  (check out 
the first link)
http://lists.ovirt.org/pipermail/users/2014-February/020913.html

So it seems this is doable, but needs a bit more finesse than I've used so far. 

Mark




> 
> > Thanks
> > Mark
> 
> -derek
> 
> -- 
>Derek Atkins 617-623-3745
>de...@ihtfp.com www.ihtfp.com
>Computer and Internet Security Consultant

___
Users mailing list
Users@ovirt.org
http://lists.ovirt.org/mailman/listinfo/users


Re: [ovirt-users] Single server hosted engine... almost there

2016-12-08 Thread Mark Steckel
[Apologize. Accidentally hit send instead of save. Continuing below...]

> - Yedidyah Bar David <d...@redhat.com> wrote:
> > On Thu, Dec 8, 2016 at 12:42 AM, Mark Steckel <m...@fix.net> wrote:
> > > Hi,
> > >
> > > OK, I reset things and tried again but was more more careful regarding 
> > > the DNS setup which I believe was correct this. In other words, the FQDNs 
> > > were resolved from both the host and the HE VM.
> > >
> > > After the latest failure I execute 'ip address' to see the state of the 
> > > interfaces. And lo and behold the /29 IP I had on eth0:1 no longer exists.
> > >
> > > So some context.
> > >
> > > The server's primary IP is a /24 with the gw being the x.y.z.1.
> > >
> > > I have have a /29 subnet to use for the VMs.
> > >
> > > I have been presuming that I place the a.b.c.1/29 on eth0:1 for the 
> > > subnet's gw and OVirt will ether keep it in place or migrate it to the 
> > > ovirtmgmt device. Instead it is deleted during "hosted-engine 
> > > --deploy".(Note, when the .1/29 is assigned to eth0:1, the IP address is 
> > > reachable from the the Internet.)
> > >
> > > Dnsmasq is configured to a) serve a.b.c.2/29 a.b.c.6/29 via DHCP and b) 
> > > to resolve unique FQDNs for each IP. The he VM set to receive the 
> > > a.b.c.2/29 address.
> > >
> > > Am I missing and or just misunderstanding something here?
> > 
> > "eth0:1" is not really a different interface.
> > 
> > Part of the deploy process is to take the interface you have chosen,
> > create a new bridge, copy part of the configuration from the nic to
> > the bridge, and add the nic to the bridge. This is one of the most
> > delicate parts of the process, the one that if fails might leave you
> > with no network access, the one due to which we recommend to run this
> > inside 'screen'. You can't do this to "eth0" and keep "eth0:1"
> > untouched. You need either a vlan interface or a separate physical
> > nic. If you feel like this, please open a bug to make 'hosted-engine
> > --deploy' notice and prevent what you tried to do. Currently it does
> > not check IP aliases.

I was creating the /29 gw IP on eth0:1 because it seems the simplest thing to 
do. There is no requirement for it to hang off of eth0.

Given that I have to hang the entire /29 subnet on the host (and VMs), and I am 
presuming that the gw IP of the /29 must be on the host, do you have a 
suggestion of how to configure this? (And to be explicit about it, do I need 
the /29 gw IP on the host to ensure the vm networking operates?)

Without the vm engine logs it is difficult to determine why the engine vm fails 
when resolving its fqdn. At this point I'm presuming it's due to a 
networking/routing issue, but am open to suggestions.


> > Another point - the script that failed is 'engine-setup'. This one
> > runs inside the engine vm, and keeps its logs in
> > /var/log/ovirt-engine/setup. If it fails again, please check/post also
> > these, if at all possible (that is, if you can access the vm).
> > Thinking about this, it might be possible for 'hosted-engine --deploy'
> > to get this log, perhaps through the virtual serial connection it
> > opens to show you the output, and save it on the host side, for easier
> > debugging. Please open a bug for this too :-)
> 

When the engine vm setup fails I am unable to connect to it via "hosted-engine 
--console". Should console access to the engine vm exist at this point? If so, 
what is the best way to access the engine vm console?

The lack access to the engine vm logs is very painful for trying to diagnose 
what is going wrong. Ideas welcomed!

Thanks
Mark



> 
> 
> 
> > 
> > Thanks, and good luck!
> > 
> > >
> > > Oh, and does ip_forwarding need to be set in the kernel? (ie 
> > > net.ipv4.ip_forward=1)
> > >
> > > Thanks
> > > Mark
> > >
> > >
> > >
> > > - Derek Atkins <de...@ihtfp.com> wrote:
> > >> Hi,
> > >>
> > >> You need to make sure resolv.conf is correct (both on the host AND on the
> > >> engine vm).
> > >>
> > >> So:   dig hostname
> > >> (without the @local-ip)
> > >>
> > >> As for the VM not coming up...  I'm not sure how to delay "engine-setup"
> > >> run.  I presume you're running an engine appliance -- I ran my own CentOS
> > >> install on the engine.  The logs imply it's suggesting you can access the
> &

Re: [ovirt-users] Single server hosted engine... almost there

2016-12-08 Thread Mark Steckel

- Yedidyah Bar David <d...@redhat.com> wrote:
> On Thu, Dec 8, 2016 at 12:42 AM, Mark Steckel <m...@fix.net> wrote:
> > Hi,
> >
> > OK, I reset things and tried again but was more more careful regarding the 
> > DNS setup which I believe was correct this. In other words, the FQDNs were 
> > resolved from both the host and the HE VM.
> >
> > After the latest failure I execute 'ip address' to see the state of the 
> > interfaces. And lo and behold the /29 IP I had on eth0:1 no longer exists.
> >
> > So some context.
> >
> > The server's primary IP is a /24 with the gw being the x.y.z.1.
> >
> > I have have a /29 subnet to use for the VMs.
> >
> > I have been presuming that I place the a.b.c.1/29 on eth0:1 for the 
> > subnet's gw and OVirt will ether keep it in place or migrate it to the 
> > ovirtmgmt device. Instead it is deleted during "hosted-engine 
> > --deploy".(Note, when the .1/29 is assigned to eth0:1, the IP address is 
> > reachable from the the Internet.)
> >
> > Dnsmasq is configured to a) serve a.b.c.2/29 a.b.c.6/29 via DHCP and b) to 
> > resolve unique FQDNs for each IP. The he VM set to receive the a.b.c.2/29 
> > address.
> >
> > Am I missing and or just misunderstanding something here?
> 
> "eth0:1" is not really a different interface.
> 
> Part of the deploy process is to take the interface you have chosen,
> create a new bridge, copy part of the configuration from the nic to
> the bridge, and add the nic to the bridge. This is one of the most
> delicate parts of the process, the one that if fails might leave you
> with no network access, the one due to which we recommend to run this
> inside 'screen'. You can't do this to "eth0" and keep "eth0:1"
> untouched. You need either a vlan interface or a separate physical
> nic. If you feel like this, please open a bug to make 'hosted-engine
> --deploy' notice and prevent what you tried to do. Currently it does
> not check IP aliases.

I was creating the /29 gw IP on eth0:1 because it seems the simplest thing to 
do. There is no requirement for it to hang off of eth0.

Without the vm engine logs it is difficult to determine why the engine vm fails 
when resolving its fqdn. At this point I'm presuming it's due to a 
networking/routing issue, but am open to suggestions.


> Another point - the script that failed is 'engine-setup'. This one
> runs inside the engine vm, and keeps its logs in
> /var/log/ovirt-engine/setup. If it fails again, please check/post also
> these, if at all possible (that is, if you can access the vm).
> Thinking about this, it might be possible for 'hosted-engine --deploy'
> to get this log, perhaps through the virtual serial connection it
> opens to show you the output, and save it on the host side, for easier
> debugging. Please open a bug for this too :-)

When the engine vm setup fails I am unable to connect to it via "hosted-engine 
--console". Is there an way to tell "hosted-engine --deploy"



> 
> Thanks, and good luck!
> 
> >
> > Oh, and does ip_forwarding need to be set in the kernel? (ie 
> > net.ipv4.ip_forward=1)
> >
> > Thanks
> > Mark
> >
> >
> >
> > - Derek Atkins <de...@ihtfp.com> wrote:
> >> Hi,
> >>
> >> You need to make sure resolv.conf is correct (both on the host AND on the
> >> engine vm).
> >>
> >> So:   dig hostname
> >> (without the @local-ip)
> >>
> >> As for the VM not coming up...  I'm not sure how to delay "engine-setup"
> >> run.  I presume you're running an engine appliance -- I ran my own CentOS
> >> install on the engine.  The logs imply it's suggesting you can access the
> >> engine VM console, but maybe it's exiting quickly?
> >>
> >> -derek
> >>
> >> On Wed, December 7, 2016 3:52 pm, Mark Steckel wrote:
> >> > I tested dnsmasq from the host by
> >> >
> >> >dig hostname @local-ip
> >> >
> >> > Worked fine.
> >> >
> >> > The engine VM never comes up to the point where I can access it via the
> >> > console...
> >> >
> >> >
> >> > - Derek Atkins <de...@ihtfp.com> wrote:
> >> >> Hi,
> >> >>
> >> >> Ensure dnsmasq is working and can be accessed by the engine VM?
> >> >> Log in to the engine VM and test from there?
> >> >> Maybe set up *real* DNS?
> >> >>
> >> >> -derek
> >> >>
> >> >> On Wed,

Re: [ovirt-users] Single server hosted engine... almost there

2016-12-07 Thread Mark Steckel
Hi,

OK, I reset things and tried again but was more more careful regarding the DNS 
setup which I believe was correct this. In other words, the FQDNs were resolved 
from both the host and the HE VM.

After the latest failure I execute 'ip address' to see the state of the 
interfaces. And lo and behold the /29 IP I had on eth0:1 no longer exists. 

So some context.

The server's primary IP is a /24 with the gw being the x.y.z.1.

I have have a /29 subnet to use for the VMs.

I have been presuming that I place the a.b.c.1/29 on eth0:1 for the subnet's gw 
and OVirt will ether keep it in place or migrate it to the ovirtmgmt device. 
Instead it is deleted during "hosted-engine --deploy".(Note, when the .1/29 is 
assigned to eth0:1, the IP address is reachable from the the Internet.)

Dnsmasq is configured to a) serve a.b.c.2/29 a.b.c.6/29 via DHCP and b) to 
resolve unique FQDNs for each IP. The he VM set to receive the a.b.c.2/29 
address.

Am I missing and or just misunderstanding something here?

Oh, and does ip_forwarding need to be set in the kernel? (ie 
net.ipv4.ip_forward=1)

Thanks
Mark



- Derek Atkins <de...@ihtfp.com> wrote:
> Hi,
> 
> You need to make sure resolv.conf is correct (both on the host AND on the
> engine vm).
> 
> So:   dig hostname
> (without the @local-ip)
> 
> As for the VM not coming up...  I'm not sure how to delay "engine-setup"
> run.  I presume you're running an engine appliance -- I ran my own CentOS
> install on the engine.  The logs imply it's suggesting you can access the
> engine VM console, but maybe it's exiting quickly?
> 
> -derek
> 
> On Wed, December 7, 2016 3:52 pm, Mark Steckel wrote:
> > I tested dnsmasq from the host by
> >
> >dig hostname @local-ip
> >
> > Worked fine.
> >
> > The engine VM never comes up to the point where I can access it via the
> > console...
> >
> >
> > - Derek Atkins <de...@ihtfp.com> wrote:
> >> Hi,
> >>
> >> Ensure dnsmasq is working and can be accessed by the engine VM?
> >> Log in to the engine VM and test from there?
> >> Maybe set up *real* DNS?
> >>
> >> -derek
> >>
> >> On Wed, December 7, 2016 3:41 pm, Mark Steckel wrote:
> >> > Hi Derek,
> >> >
> >> > - Derek Atkins <de...@ihtfp.com> wrote:
> >> >> Hi Mark,
> >> >>
> >> >> The error is correct, hosted-engine-1.pcstrac.com is not a valid
> >> >> hostname:
> >> >>
> >> >> $ host hosted-engine-1.pcstrac.com
> >> >> $
> >> >>
> >> >> I'm lost, tho -- was this an error that occurred on the host during
> >> >> hosted-engine --deploy, or was it an error that occurred in the
> >> hosted
> >> >> enging VM when running engine-setup?
> >> >
> >> > I believe when it occurred when the running the engine-setup.
> >> >
> >> >
> >> >> If the former, you need to ensure that you have a real DNS name for
> >> your
> >> >> ovirt engine.  It's unclear (to me) that using /etc/hosts is
> >> sufficient.
> >> >> However looking at the logs, it looks like it can locally resolve (to
> >> >> xx.yy.18.122).
> >> >
> >> > Yep. I tested things to make sure it could resolve before I started
> >> the
> >> > 'hosted-engine --deploy'.
> >> >
> >> >> You might need to answer "Yes" to the /etc/hosts question..
> >> >
> >> > I did answer "Yes".
> >> >
> >> >
> >> >> The log seems to get far enough along that it presents you the engine
> >> vm
> >> >> console URL?  It looks like the issue is that the engine vm cannot
> >> >> resolve
> >> >> its own name.
> >> >
> >> > That is my take as well.
> >> >
> >> > Scratching my head as I config'ed dnsmasq to provide local dns and to
> >> read
> >> > from /etc/hosts for hosted-engine-1.pcstrac.com.
> >> >
> >> > The only thing I think I flubbed was neglecting to add the host's IP
> >> to
> >> > the host's /etc/resolv.conf.
> >> >
> >> > Scrubbing and staring again.
> >> >
> >> > Mark
> >> >
> >> >
> >> >>
> >> >> -derek
> >> >>
> >> >> On Wed, December 7, 2016 3:13 pm, Mark Steckel wrote:
> >> >> > Folks,
> >> >> >

Re: [ovirt-users] Single server hosted engine... almost there

2016-12-07 Thread Mark Steckel
I tested dnsmasq from the host by

   dig hostname @local-ip

Worked fine.

The engine VM never comes up to the point where I can access it via the 
console...


- Derek Atkins <de...@ihtfp.com> wrote:
> Hi,
> 
> Ensure dnsmasq is working and can be accessed by the engine VM?
> Log in to the engine VM and test from there?
> Maybe set up *real* DNS?
> 
> -derek
> 
> On Wed, December 7, 2016 3:41 pm, Mark Steckel wrote:
> > Hi Derek,
> >
> > - Derek Atkins <de...@ihtfp.com> wrote:
> >> Hi Mark,
> >>
> >> The error is correct, hosted-engine-1.pcstrac.com is not a valid
> >> hostname:
> >>
> >> $ host hosted-engine-1.pcstrac.com
> >> $
> >>
> >> I'm lost, tho -- was this an error that occurred on the host during
> >> hosted-engine --deploy, or was it an error that occurred in the hosted
> >> enging VM when running engine-setup?
> >
> > I believe when it occurred when the running the engine-setup.
> >
> >
> >> If the former, you need to ensure that you have a real DNS name for your
> >> ovirt engine.  It's unclear (to me) that using /etc/hosts is sufficient.
> >> However looking at the logs, it looks like it can locally resolve (to
> >> xx.yy.18.122).
> >
> > Yep. I tested things to make sure it could resolve before I started the
> > 'hosted-engine --deploy'.
> >
> >> You might need to answer "Yes" to the /etc/hosts question..
> >
> > I did answer "Yes".
> >
> >
> >> The log seems to get far enough along that it presents you the engine vm
> >> console URL?  It looks like the issue is that the engine vm cannot
> >> resolve
> >> its own name.
> >
> > That is my take as well.
> >
> > Scratching my head as I config'ed dnsmasq to provide local dns and to read
> > from /etc/hosts for hosted-engine-1.pcstrac.com.
> >
> > The only thing I think I flubbed was neglecting to add the host's IP to
> > the host's /etc/resolv.conf.
> >
> > Scrubbing and staring again.
> >
> > Mark
> >
> >
> >>
> >> -derek
> >>
> >> On Wed, December 7, 2016 3:13 pm, Mark Steckel wrote:
> >> > Folks,
> >> >
> >> > Thanks to Didi in another thread I'm making progress. (Lesson learned,
> >> > choose 'disk' and not 'cdrom' when using the he-appliance.)
> >> >
> >> > So I reset to a fresh CentOS 7, installed various software packages
> >> > including ovirt.
> >> >
> >> > I configed eth0 with a /32 public IP. I also added an alias for a
> >> > x.x.x.1/29 on eth0:1.
> >> >
> >> > Finally I config'ed dnsmasq to provide both dhcp and dns (ensuring
> >> that it
> >> > will read from /etc/hosts before forwarding dns requests) and added
> >> the
> >> > IPs and hostsnames to /etc/hosts from the /29 IPs which are to be used
> >> by
> >> > the VMs.
> >> >
> >> > Things proceeded nicely till resolving the he vm fqdn. (I tested to
> >> make
> >> > sure that the he vm fqdm would resolve **Before** I ran 'hosted-engine
> >> > --deploy'.)
> >> >
> >> >   |-   --== NETWORK CONFIGURATION ==--
> >> >   |-
> >> >   |- [ ERROR ] Host name is not valid:
> >> hosted-engine-1.pcstrac.com
> >> > did not resolve into an IP address
> >> >   |- [ ERROR ] Failed to execute stage 'Environment
> >> > customization': Host name is not valid:
> >> > hosted-engine-1.pcstrac.com did not resolve into an IP address
> >> >   |- [ INFO  ] Stage: Clean up
> >> >   |-   Log file is located at
> >> > /var/log/ovirt-engine/setup/ovirt-engine-setup-20161207193757-6i03xg.log
> >> >   |- [ INFO  ] Generating answer file
> >> > '/var/lib/ovirt-engine/setup/answers/20161207193758-setup.conf'
> >> >   |- [ INFO  ] Stage: Pre-termination
> >> >   |- [ INFO  ] Stage: Termination
> >> >   |- [ ERROR ] Execution of setup failed
> >> >   |- HE_APPLIANCE_ENGINE_SETUP_FAIL
> >> > [ ERROR ] Engine setup failed on the appliance
> >> > [ ERROR ] Failed to execute stage 'Closing up': Engine setup
> >> failed on
> >> > the appliance Please check its log on the appliance.
> >> >
> >> >
> >> > The one thing I forgot is to update /etc/resolv.conf to include the
> >> host
> >> > though I don't know if this matters...
> >> >
> >> > Logs attached.
> >> >
> >> > I suspect I've very close to having this working but am admittedly
> >> > stumped.
> >> >
> >> > Pointers appreciated.
> >> >
> >> > Thanks
> >> > Mark
> >> >
> >> >
> >> > ___
> >> > Users mailing list
> >> > Users@ovirt.org
> >> > http://lists.ovirt.org/mailman/listinfo/users
> >> >
> >>
> >>
> >> --
> >>Derek Atkins 617-623-3745
> >>de...@ihtfp.com www.ihtfp.com
> >>Computer and Internet Security Consultant
> >>
> >
> >
> 
> 
> -- 
>Derek Atkins 617-623-3745
>de...@ihtfp.com www.ihtfp.com
>Computer and Internet Security Consultant
> 

___
Users mailing list
Users@ovirt.org
http://lists.ovirt.org/mailman/listinfo/users


Re: [ovirt-users] Single server hosted engine... almost there

2016-12-07 Thread Mark Steckel
Hi Derek,

- Derek Atkins <de...@ihtfp.com> wrote:
> Hi Mark,
> 
> The error is correct, hosted-engine-1.pcstrac.com is not a valid hostname:
> 
> $ host hosted-engine-1.pcstrac.com
> $
> 
> I'm lost, tho -- was this an error that occurred on the host during
> hosted-engine --deploy, or was it an error that occurred in the hosted
> enging VM when running engine-setup?

I believe when it occurred when the running the engine-setup.


> If the former, you need to ensure that you have a real DNS name for your
> ovirt engine.  It's unclear (to me) that using /etc/hosts is sufficient.
> However looking at the logs, it looks like it can locally resolve (to
> xx.yy.18.122).

Yep. I tested things to make sure it could resolve before I started the 
'hosted-engine --deploy'.

> You might need to answer "Yes" to the /etc/hosts question..

I did answer "Yes".


> The log seems to get far enough along that it presents you the engine vm
> console URL?  It looks like the issue is that the engine vm cannot resolve
> its own name.

That is my take as well.

Scratching my head as I config'ed dnsmasq to provide local dns and to read from 
/etc/hosts for hosted-engine-1.pcstrac.com.

The only thing I think I flubbed was neglecting to add the host's IP to the 
host's /etc/resolv.conf.

Scrubbing and staring again. 

Mark


> 
> -derek
> 
> On Wed, December 7, 2016 3:13 pm, Mark Steckel wrote:
> > Folks,
> >
> > Thanks to Didi in another thread I'm making progress. (Lesson learned,
> > choose 'disk' and not 'cdrom' when using the he-appliance.)
> >
> > So I reset to a fresh CentOS 7, installed various software packages
> > including ovirt.
> >
> > I configed eth0 with a /32 public IP. I also added an alias for a
> > x.x.x.1/29 on eth0:1.
> >
> > Finally I config'ed dnsmasq to provide both dhcp and dns (ensuring that it
> > will read from /etc/hosts before forwarding dns requests) and added the
> > IPs and hostsnames to /etc/hosts from the /29 IPs which are to be used by
> > the VMs.
> >
> > Things proceeded nicely till resolving the he vm fqdn. (I tested to make
> > sure that the he vm fqdm would resolve **Before** I ran 'hosted-engine
> > --deploy'.)
> >
> >   |-   --== NETWORK CONFIGURATION ==--
> >   |-
> >   |- [ ERROR ] Host name is not valid: hosted-engine-1.pcstrac.com
> > did not resolve into an IP address
> >   |- [ ERROR ] Failed to execute stage 'Environment
> > customization': Host name is not valid:
> > hosted-engine-1.pcstrac.com did not resolve into an IP address
> >   |- [ INFO  ] Stage: Clean up
> >   |-   Log file is located at
> > /var/log/ovirt-engine/setup/ovirt-engine-setup-20161207193757-6i03xg.log
> >   |- [ INFO  ] Generating answer file
> > '/var/lib/ovirt-engine/setup/answers/20161207193758-setup.conf'
> >   |- [ INFO  ] Stage: Pre-termination
> >   |- [ INFO  ] Stage: Termination
> >   |- [ ERROR ] Execution of setup failed
> >   |- HE_APPLIANCE_ENGINE_SETUP_FAIL
> > [ ERROR ] Engine setup failed on the appliance
> > [ ERROR ] Failed to execute stage 'Closing up': Engine setup failed on
> > the appliance Please check its log on the appliance.
> >
> >
> > The one thing I forgot is to update /etc/resolv.conf to include the host
> > though I don't know if this matters...
> >
> > Logs attached.
> >
> > I suspect I've very close to having this working but am admittedly
> > stumped.
> >
> > Pointers appreciated.
> >
> > Thanks
> > Mark
> >
> >
> > ___
> > Users mailing list
> > Users@ovirt.org
> > http://lists.ovirt.org/mailman/listinfo/users
> >
> 
> 
> -- 
>Derek Atkins 617-623-3745
>de...@ihtfp.com www.ihtfp.com
>Computer and Internet Security Consultant
> 

___
Users mailing list
Users@ovirt.org
http://lists.ovirt.org/mailman/listinfo/users


[ovirt-users] Single server hosted engine... almost there

2016-12-07 Thread Mark Steckel
Folks,

Thanks to Didi in another thread I'm making progress. (Lesson learned, choose 
'disk' and not 'cdrom' when using the he-appliance.)

So I reset to a fresh CentOS 7, installed various software packages including 
ovirt.

I configed eth0 with a /32 public IP. I also added an alias for a x.x.x.1/29 on 
eth0:1.

Finally I config'ed dnsmasq to provide both dhcp and dns (ensuring that it will 
read from /etc/hosts before forwarding dns requests) and added the IPs and 
hostsnames to /etc/hosts from the /29 IPs which are to be used by the VMs.

Things proceeded nicely till resolving the he vm fqdn. (I tested to make sure 
that the he vm fqdm would resolve **Before** I ran 'hosted-engine --deploy'.)

  |-   --== NETWORK CONFIGURATION ==--
  |-  
  |- [ ERROR ] Host name is not valid: hosted-engine-1.pcstrac.com did 
not resolve into an IP address
  |- [ ERROR ] Failed to execute stage 'Environment customization': 
Host name is not valid: hosted-engine-1.pcstrac.com did not resolve into an IP 
address
  |- [ INFO  ] Stage: Clean up
  |-   Log file is located at 
/var/log/ovirt-engine/setup/ovirt-engine-setup-20161207193757-6i03xg.log
  |- [ INFO  ] Generating answer file 
'/var/lib/ovirt-engine/setup/answers/20161207193758-setup.conf'
  |- [ INFO  ] Stage: Pre-termination
  |- [ INFO  ] Stage: Termination
  |- [ ERROR ] Execution of setup failed
  |- HE_APPLIANCE_ENGINE_SETUP_FAIL
[ ERROR ] Engine setup failed on the appliance
[ ERROR ] Failed to execute stage 'Closing up': Engine setup failed on the 
appliance Please check its log on the appliance. 


The one thing I forgot is to update /etc/resolv.conf to include the host though 
I don't know if this matters...

Logs attached.

I suspect I've very close to having this working but am admittedly stumped.

Pointers appreciated.

Thanks
Mark




ovirt-hosted-engine-setup-20161207202846-lzdp1w.log.gz
Description: GNU Zip compressed data


answers-20161207203800.conf.gz
Description: GNU Zip compressed data
___
Users mailing list
Users@ovirt.org
http://lists.ovirt.org/mailman/listinfo/users


Re: [ovirt-users] hosted-engine --deploy hanging, vm not responding

2016-12-07 Thread Mark Steckel
- Yedidyah Bar David <d...@redhat.com> wrote:
> On Wed, Dec 7, 2016 at 4:46 PM, Mark Steckel <m...@fix.net> wrote:
> > Log attached.
> >
> > - Yedidyah Bar David <d...@redhat.com> wrote:
> >> On Wed, Dec 7, 2016 at 4:36 PM, Mark Steckel <m...@fix.net> wrote:
> >> > Folks,
> >> >
> >> > I executed "hosted-engine --deploy" on a fresh CentOS 7.2 install. 
> >> > Before executing the cmd I also installed the he-appliance. (Also ran 
> >> > yum update, installed a few packages and rebooted before doing the 
> >> > hosted engine deploy.)
> >> >
> >> > The process seems to go well but then it hangs here:
> >> >
> >> >   The VM has been started.
> >> >   To continue please install OS and shutdown or reboot the VM.
> >> >
> >> >   Make a selection from the options below:
> >> >   (1) Continue setup - OS installation is complete
> >> >   (2) Abort setup
> >> >   (3) Power off and restart the VM
> >> >   (4) Destroy VM and abort setup
> >> >
> >> >   (1, 2, 3, 4)[1]: 1
> >> >
> >> >   Please reboot or shutdown the VM.
> >> >
> >> >   Verifying shutdown...
> >> >
> >> > From another terminal window I tried accessing the console but received 
> >> > the following:
> >> >
> >> > # hosted-engine --console
> 
> IIRC this now connects you to a serial console, not graphical.

Which is what I was expecting and am comfortable with. (I've very comfortable 
with using kickstart, virsh, virt-install, et al and and a serial console, but 
totally new to OVirt and cloud init.)

> It also told you:
> 
> You can also graphically connect to the VM from your system with the
> following command:
> remote-viewer vnc://dev-vm-host:5900
> 
> Did you try this?

In a previous iteration but without success.


> See also:
> 
> http://www.ovirt.org/documentation/admin-guide/hosted-engine-console/
> 
> However, if this is your first installation, with simple/standard needs,
> it's much simpler to use the appliance. Install the package
> 'ovirt-engine-appliance',
> then choose to boot from 'disk'.

Ah I did install the ovirt-engine-appliance, but choose cdrom and pointed 
it to a Centos 7.2 iso.

Let me reset and try again using the appliance and 'disk'.

My needs are simple, so hopefully this will do the trick.

Thanks
Mark



> 
> Best,
> -- 
> Didi

___
Users mailing list
Users@ovirt.org
http://lists.ovirt.org/mailman/listinfo/users


[ovirt-users] hosted-engine --deploy hanging, vm not responding

2016-12-07 Thread Mark Steckel
Folks,

I executed "hosted-engine --deploy" on a fresh CentOS 7.2 install. Before 
executing the cmd I also installed the he-appliance. (Also ran yum update, 
installed a few packages and rebooted before doing the hosted engine deploy.)

The process seems to go well but then it hangs here:

  The VM has been started.
  To continue please install OS and shutdown or reboot the VM.

  Make a selection from the options below:
  (1) Continue setup - OS installation is complete
  (2) Abort setup
  (3) Power off and restart the VM
  (4) Destroy VM and abort setup

  (1, 2, 3, 4)[1]: 1

  Please reboot or shutdown the VM.

  Verifying shutdown...

>From another terminal window I tried accessing the console but received the 
>following:

# hosted-engine --console
The engine VM is running on this host
Connected to domain HostedEngine
Escape character is ^]
error: internal error: character device console0 is not using a PTY

I've also tried option 3 above, but then it comes back with 

Checking for oVirt-Engine status at hosted-engine-1.example.com...
[ INFO  ] Engine is still unreachable
oVirt-Engine health status page is not yet reachable.

I am admittedly mystified at this point.

Any ideas?

Thanks
Mark

___
Users mailing list
Users@ovirt.org
http://lists.ovirt.org/mailman/listinfo/users


Re: [ovirt-users] Hosted-engine --deploy FQDN questions

2016-12-07 Thread Mark Steckel
Yedidyah - very helpful! Thanks.

A follow-up question re the FQDN for the hosted engine: My understanding is 
that the FQDN must be resolvable when "hosted-engine --deploy" is executed. 
However, should the IP that the FQDN resolves to also be assigned/up when 
"hosted-engine --deploy" is executed?



- Yedidyah Bar David <d...@redhat.com> wrote:
> On Wed, Dec 7, 2016 at 11:36 AM, Mark Steckel <m...@fix.net> wrote:
> > Marcin,
> >
> > - Marcin Mirecki <mmire...@redhat.com> wrote:
> >> Mark,
> >>
> >> >   Enter the name which will be used to identify this host inside 
> >> > the
> >> >   Administrator Portal [hosted_engine_1]:
> >>
> >> This is the name used for the host inside the Administrator Portal, so 
> >> basically
> >> the name of the VM inside the system.
> >> This does not have to be the hostname, but there are also no objection for 
> >> it.
> >>
> >>
> >> >   Engine FQDN:  []:
> >> Yes, you are correct. This must be the FQDN of the host, resolvable to IP.
> >> This fqdn will be used to access the administration portal.
> >
> > If I understand you correctly, both questions apply to the hosted engine 
> > vm. Correct?
> 
> No.
> 
> The first question is about the host, but not about its address or dns name.
> It's about the name it will have in the engine, the one you see in the admin 
> ui,
> in "Hosts", as "Name". After too many questions about this question, we 
> decided
> to remove it, and in 4.1 it will simply default to the hostname. You'll still 
> be
> able to set it by manually editing the answer file or passing otopi
> env, but will
> not be prompted for it.
> 
> The second question is indeed about the name that will be used to access
> the engine vm.
> 
> Then there is a third item, which we do not ask about: The name that the
> engine should use to access the host. This is what you see in the admin ui,
> in "Hostname/IP". This item is determined the following way, for the first
> host: You are prompted for a NIC to use for the management bridge, we check
> the IP address of this NIC, then do a reverse-lookup (gethostbyaddr) on this
> address, and use the result. So you should make sure that this nic has an
> IP address, that this address has a name (in /etc/hosts or dns), and that
> this name will also be resolvable and point to the host, when used inside
> the engine vm (again, by either using dns or manually setting it in
> /etc/hosts there).
> 
> >
> > (If so, I'm glad I asked, because I initially and incorrectly thought that 
> > the first question referred to the bare metal machine that hosts the hosted 
> > engine vm.)
> 
> Hopefully the above clarifies this. Please do not hesitate to ask if
> there are still questions. Also, suggestions for better texts, to make
> this simpler for the admin, are more than welcome! :-)
> 
> Best,
> 
> >
> > Thanks
> > Mark
> >
> >
> >
> >>
> >> Marcin
> >>
> >>
> >> - Original Message -
> >> > From: "Mark Steckel" <m...@fix.net>
> >> > To: users@ovirt.org
> >> > Sent: Wednesday, December 7, 2016 6:08:38 AM
> >> > Subject: [ovirt-users] Hosted-engine --deploy FQDN questions
> >> >
> >> > Folks,
> >> >
> >> > I'm an OVirt newbie having troubles setting up my first Hosted Engine 
> >> > and am
> >> > stumbling. In this case I think it may be because of the following two
> >> > set-up questions.
> >> >
> >> >   Enter the name which will be used to identify this host inside 
> >> > the
> >> >   Administrator Portal [hosted_engine_1]:
> >> >   Please provide the FQDN for the engine you would like to use.
> >> >   This needs to match the FQDN that you will use for the engine
> >> >   installation within the VM.
> >> >   Note: This will be the FQDN of the VM you are now going to 
> >> > create,
> >> >   it should not point to the base host or to any other existing
> >> >   machine.
> >> >   Engine FQDN:  []:
> >> >
> >> > My read of this is that the first question is asking for the name of the
> >> > host, while the second question is asking for the name (FQDN) of the 
> >> > guest
> >> > vm which will be the hosted-engine. Is this correct?
> >> >
> >> > I'm also presuming that a) the first question should be the hostname of 
> >> > the
> >> > host, and b) that both the host and guest hostnames should resolve to IP
> >> > addresses.
> >> >
> >> > Thanks
> >> > Mark
> >> > ___
> >> > Users mailing list
> >> > Users@ovirt.org
> >> > http://lists.ovirt.org/mailman/listinfo/users
> >> >
> >
> > ___
> > Users mailing list
> > Users@ovirt.org
> > http://lists.ovirt.org/mailman/listinfo/users
> 
> 
> 
> -- 
> Didi

___
Users mailing list
Users@ovirt.org
http://lists.ovirt.org/mailman/listinfo/users


Re: [ovirt-users] Hosted-engine --deploy FQDN questions

2016-12-07 Thread Mark Steckel
Marcin,

- Marcin Mirecki <mmire...@redhat.com> wrote:
> Mark,
> 
> >   Enter the name which will be used to identify this host inside the
> >   Administrator Portal [hosted_engine_1]:
> 
> This is the name used for the host inside the Administrator Portal, so 
> basically
> the name of the VM inside the system.
> This does not have to be the hostname, but there are also no objection for it.
> 
> 
> >   Engine FQDN:  []:
> Yes, you are correct. This must be the FQDN of the host, resolvable to IP.
> This fqdn will be used to access the administration portal.

If I understand you correctly, both questions apply to the hosted engine vm. 
Correct?

(If so, I'm glad I asked, because I initially and incorrectly thought that the 
first question referred to the bare metal machine that hosts the hosted engine 
vm.)

Thanks
Mark



> 
> Marcin
> 
> 
> - Original Message -
> > From: "Mark Steckel" <m...@fix.net>
> > To: users@ovirt.org
> > Sent: Wednesday, December 7, 2016 6:08:38 AM
> > Subject: [ovirt-users] Hosted-engine --deploy FQDN questions
> > 
> > Folks,
> > 
> > I'm an OVirt newbie having troubles setting up my first Hosted Engine and am
> > stumbling. In this case I think it may be because of the following two
> > set-up questions.
> > 
> >   Enter the name which will be used to identify this host inside the
> >   Administrator Portal [hosted_engine_1]:
> >   Please provide the FQDN for the engine you would like to use.
> >   This needs to match the FQDN that you will use for the engine
> >   installation within the VM.
> >   Note: This will be the FQDN of the VM you are now going to create,
> >   it should not point to the base host or to any other existing
> >   machine.
> >   Engine FQDN:  []:
> > 
> > My read of this is that the first question is asking for the name of the
> > host, while the second question is asking for the name (FQDN) of the guest
> > vm which will be the hosted-engine. Is this correct?
> > 
> > I'm also presuming that a) the first question should be the hostname of the
> > host, and b) that both the host and guest hostnames should resolve to IP
> > addresses.
> > 
> > Thanks
> > Mark
> > ___
> > Users mailing list
> > Users@ovirt.org
> > http://lists.ovirt.org/mailman/listinfo/users
> > 

___
Users mailing list
Users@ovirt.org
http://lists.ovirt.org/mailman/listinfo/users


[ovirt-users] Hosted-engine --deploy FQDN questions

2016-12-06 Thread Mark Steckel
Folks,

I'm an OVirt newbie having troubles setting up my first Hosted Engine and am 
stumbling. In this case I think it may be because of the following two set-up 
questions.

  Enter the name which will be used to identify this host inside the 
Administrator Portal [hosted_engine_1]:
  Please provide the FQDN for the engine you would like to use.
  This needs to match the FQDN that you will use for the engine 
installation within the VM.
  Note: This will be the FQDN of the VM you are now going to create,
  it should not point to the base host or to any other existing machine.
  Engine FQDN:  []: 

My read of this is that the first question is asking for the name of the host, 
while the second question is asking for the name (FQDN) of the guest vm which 
will be the hosted-engine. Is this correct?

I'm also presuming that a) the first question should be the hostname of the 
host, and b) that both the host and guest hostnames should resolve to IP 
addresses.

Thanks
Mark
___
Users mailing list
Users@ovirt.org
http://lists.ovirt.org/mailman/listinfo/users


Re: [ovirt-users] Self hosted single server network requirements

2016-12-05 Thread Mark Steckel
Follow-up - I finally discovered the source of my networking troubles.

The provider (Hetzner) configures the primary IP in a somewhat odd manner for 
Cent OS 7.2.

For instance, here is /etc/sysconfig/network-scripts/ifcfg-eth0 (lightly edited)

DEVICE=eth0
ONBOOT=yes
BOOTPROTO=none
IPADDR=A.B.4.9
NETMASK=255.255.255.255
SCOPE="peer A.B.4.1"

And /etc/sysconfig/network-scripts/route-eth0

ADDRESS0=0.0.0.0
NETMASK0=0.0.0.0
GATEWAY0=A.B.4.1

The key thing is the SCOPE line.

This creates a private link between the server's IP and the gw IP. The server's 
IP address no longer has a netmask, which is now specified on the gw IP.

The odd network config appears to confuse the hosted-engine deploy process 
because it was unable to configure the ovirtmgmt bridge in a working manner.

Once I delete route-eth0 and changed ifcfg-eth0 to a more typical configuration 
all started working.

Now I just need to figure out how to configure the /29 for the VMs.

Thanks
Mark


- Derek Atkins <de...@ihtfp.com> wrote:
> Hi,
> 
> On Mon, November 21, 2016 4:30 pm, Mark Steckel wrote:
> >
> [snip]
> >> >> > Advice so far seems to be:
> >> >> > * Use 'screen' when deploying. Easy
> >> >> > * Don't use/disable Network-Manager. Easy
> >> >> > * Preconfigure the ovirtmgmt bridge. I've got questions...
> >> >> >
> >> >> > The server has a public /32 as the primary IP, and a public /29
> >> which
> >> >> > will be used for the VMs.
> >> >> >
> >> >> > Besides creating the ovirtmgmt bridge is there anything specific
> >> for
> >> >> > how I should configure it?
> [snip]
> >
> > Yeah, I was hoping that would be the case for me too. :-)
> 
> For what it's worth, it took me about 4 tries to get it all working.
> I wound up using a script I found to clean the host and re-install it all.
>  Of course the cleanup process let the firewall in a state where it
> blocked all traffic (including SSH), but I figured that part out on the
> 2nd try so added it back into my script for the 3rd.  ;)
> 
> The other difference is that I had already created a bond0 interface which
> was my default (with a non-NM-controlled static network).  However, that
> shouldn't have made a difference.
> 
> >> What did your /etc/sysconfig/network-scripts/ifcfg- file look like?
> >> (And what does the ifcfg-ovirtmgmt file look like)?
> >
> > Sadly, thinking I messed things up I scrubbed the machine and started
> > over. I have a fresh CentOS 7.2 install waiting to run 'hosted-engine
> > --deploy' on it once I have a better sense what if anything I need to
> > prepare from a networking stand point.
> 
> Okay, so go and try it!  :)
> 
> Worst case, you need to run hosted-engine-cleanup.sh and then reset the
> firewall and reboot, and then re-install everything:
> 
> https://access.redhat.com/documentation/en/red-hat-virtualization/4.0/paged/self-hosted-engine-guide/chapter-2-deploying-self-hosted-engine
> http://www.ovirt.org/documentation/how-to/hosted-engine/#fresh-install
> 
> [snip]
> >> >> As for the /29 -- don't worry about it now, that would be a routing
> >> >> issue you can apply later.  Is it the same network as the /32?  Or is
> >> it
> >> >> a different network?
> >> >
> >> > Different.
> >>
> >> I assume both networks are available on your host interface?
> >
> > At this point only the /32 is on the host interface. The /29 is not
> > assigned at the moment.
> 
> You shouldn't need to "assign" anything in the /29 to the host.  All
> that's important is that the physical network can reach the /29.  I.e.,
> you could do something like:
> 
>  /32   /32/29
> router --- host   VMs
>  /29
> 
> The host will bridge the network to the VMs, but it can be on a different
> network.
> 
> > Mark
> 
> -derek
> 
> -- 
>Derek Atkins 617-623-3745
>de...@ihtfp.com www.ihtfp.com
>Computer and Internet Security Consultant
> 

___
Users mailing list
Users@ovirt.org
http://lists.ovirt.org/mailman/listinfo/users


Re: [ovirt-users] Self hosted single server network requirements

2016-11-21 Thread Mark Steckel

- Derek Atkins <de...@ihtfp.com> wrote:
> Hi,
> 
> On Mon, November 21, 2016 4:21 pm, Mark Steckel wrote:
> >
> > - Derek Atkins <de...@ihtfp.com> wrote:
> >> Hi,
> >>
> >> Mark Steckel <m...@fix.net> writes:
> >>
> >> > Thanks all who have responded so far.
> >> >
> >> > Advice so far seems to be:
> >> > * Use 'screen' when deploying. Easy
> >> > * Don't use/disable Network-Manager. Easy
> >> > * Preconfigure the ovirtmgmt bridge. I've got questions...
> >> >
> >> > The server has a public /32 as the primary IP, and a public /29 which
> >> > will be used for the VMs.
> >> >
> >> > Besides creating the ovirtmgmt bridge is there anything specific for
> >> > how I should configure it?
> >>
> >> My recommendation is that you just set up non-NM-controlled static
> >> network using your public /32.  Then the hosted-engine --deploy process
> >> should take that config and apply it to ovirtmgmt bridge.  At least,
> >> that's what happened for me when I did it.  I don't think you need to
> >> set up the ovirtmgmt bridge manually.
> >
> > This is what I initially did and then lost Internet access when the /32
> > was migrated to the ovirtmgmt bridge.
> >
> > I then used KVM console access to access the box, but it could no longer
> > access it's public gateway. It was at this point then I surmised that
> > something was amiss.
> 
> Hmm.  That's odd.  "If worked for me"..

Yeah, I was hoping that would be the case for me too. :-)

> 
> What did your /etc/sysconfig/network-scripts/ifcfg- file look like? 
> (And what does the ifcfg-ovirtmgmt file look like)?

Sadly, thinking I messed things up I scrubbed the machine and started over. I 
have a fresh CentOS 7.2 install waiting to run 'hosted-engine --deploy' on it 
once I have a better sense what if anything I need to prepare from a networking 
stand point.





> 
> >
> >>
> >> As for the /29 -- don't worry about it now, that would be a routing
> >> issue you can apply later.  Is it the same network as the /32?  Or is it
> >> a different network?
> >
> > Different.
> 
> I assume both networks are available on your host interface?

At this point only the /32 is on the host interface. The /29 is not assigned at 
the moment.

Mark



> 
> -derek
> 
> -- 
>Derek Atkins 617-623-3745
>de...@ihtfp.com www.ihtfp.com
>Computer and Internet Security Consultant
> 

___
Users mailing list
Users@ovirt.org
http://lists.ovirt.org/mailman/listinfo/users


Re: [ovirt-users] Self hosted single server network requirements

2016-11-21 Thread Mark Steckel

- Derek Atkins <de...@ihtfp.com> wrote:
> Hi,
> 
> Mark Steckel <m...@fix.net> writes:
> 
> > Thanks all who have responded so far.
> >
> > Advice so far seems to be:
> > * Use 'screen' when deploying. Easy
> > * Don't use/disable Network-Manager. Easy
> > * Preconfigure the ovirtmgmt bridge. I've got questions...
> >
> > The server has a public /32 as the primary IP, and a public /29 which
> > will be used for the VMs.
> >
> > Besides creating the ovirtmgmt bridge is there anything specific for
> > how I should configure it?
> 
> My recommendation is that you just set up non-NM-controlled static
> network using your public /32.  Then the hosted-engine --deploy process
> should take that config and apply it to ovirtmgmt bridge.  At least,
> that's what happened for me when I did it.  I don't think you need to
> set up the ovirtmgmt bridge manually.

This is what I initially did and then lost Internet access when the /32 was 
migrated to the ovirtmgmt bridge.

I then used KVM console access to access the box, but it could no longer access 
it's public gateway. It was at this point then I surmised that something was 
amiss.

> 
> As for the /29 -- don't worry about it now, that would be a routing
> issue you can apply later.  Is it the same network as the /32?  Or is it
> a different network?

Different.


> 
> > Thanks
> > Mark
> 
> -derek
> 
> > - Paul-Erik Törrönen <pol...@poltsi.fi> wrote:
> >> On 2016-11-19 11:28, Joop wrote:
> >> > I have never setup such a server but if you create the ovirtmgmt bridge
> >> > first then the deploy will leave it alone and you won't lose network
> >> > connectivity.
> >> 
> >> I've set up almost the described combination (I do run the vm-engine on 
> >> a separate laptop), and found that running the commandline stuff in a 
> >> screen helps a lot, the setup commands can then complete instead of 
> >> being interrupted as your (ssh-)session is killed.
> >> 
> >> I also enountered the same issue of network connection loss as the 
> >> ovirtmgmt-interface took over my primary connection, but I was able to 
> >> continue as I  had several network devices on my hardware which I had 
> >> already configured, and was able to access the server through them.
> >> 
> >> If you only have one network interface, then I would recommend running 
> >> the commands in a screen, and in the case of losing the connection, 
> >> reconnect to the screen through the KVM.
> >> 
> >> My 0.02€
> >> 
> >> Poltsi
> >> ___
> >> Users mailing list
> >> Users@ovirt.org
> >> http://lists.ovirt.org/mailman/listinfo/users
> >
> > ___
> > Users mailing list
> > Users@ovirt.org
> > http://lists.ovirt.org/mailman/listinfo/users
> 
> -- 
>Derek Atkins 617-623-3745
>de...@ihtfp.com www.ihtfp.com
>Computer and Internet Security Consultant

___
Users mailing list
Users@ovirt.org
http://lists.ovirt.org/mailman/listinfo/users


Re: [ovirt-users] Self hosted single server network requirements

2016-11-21 Thread Mark Steckel
Thanks all who have responded so far.

Advice so far seems to be:
* Use 'screen' when deploying. Easy
* Don't use/disable Network-Manager. Easy
* Preconfigure the ovirtmgmt bridge. I've got questions...

The server has a public /32 as the primary IP, and a public /29 which will be 
used for the VMs.

Besides creating the ovirtmgmt bridge is there anything specific for how I 
should configure it?

Thanks
Mark


- Paul-Erik Törrönen  wrote:
> On 2016-11-19 11:28, Joop wrote:
> > I have never setup such a server but if you create the ovirtmgmt bridge
> > first then the deploy will leave it alone and you won't lose network
> > connectivity.
> 
> I've set up almost the described combination (I do run the vm-engine on 
> a separate laptop), and found that running the commandline stuff in a 
> screen helps a lot, the setup commands can then complete instead of 
> being interrupted as your (ssh-)session is killed.
> 
> I also enountered the same issue of network connection loss as the 
> ovirtmgmt-interface took over my primary connection, but I was able to 
> continue as I  had several network devices on my hardware which I had 
> already configured, and was able to access the server through them.
> 
> If you only have one network interface, then I would recommend running 
> the commands in a screen, and in the case of losing the connection, 
> reconnect to the screen through the KVM.
> 
> My 0.02€
> 
> Poltsi
> ___
> Users mailing list
> Users@ovirt.org
> http://lists.ovirt.org/mailman/listinfo/users

___
Users mailing list
Users@ovirt.org
http://lists.ovirt.org/mailman/listinfo/users


Re: [ovirt-users] Self hosted single server network requirements

2016-11-21 Thread Mark Steckel

- Yedidyah Bar David <d...@redhat.com> wrote:
> On Sat, Nov 19, 2016 at 11:28 AM, Joop <jvdw...@xs4all.nl> wrote:
> > On 18-11-2016 23:47, Mark Steckel wrote:
> >> Hi folks,
> >>
> >> I'm a complete OVirt newbie trying to set up a self hosted, single server 
> >> and looking for some pointers to get going... (While new to OVirt, I'm 
> >> long time sysadmin so not totally clueless.)
> 
> Welcome :-)

Thanks!


> 
> >>
> >> The server I'm using has a 4-core CPU, 64 GB of ram, and a pair of 500 GB 
> >> SSDs set up with RAID 1 and running CentOS 7.2. (I do not have physical 
> >> access to the server but can get KVM access when required.)
> >>
> >> The goal is to set up this server as a self hosted, single server OVirt 
> >> platform. Nothing mission critical, just want to be able to spin up VMs 
> >> when needed and destroy them afterwards.
> >>
> >> Trying to use OVirt 4.0.4 (now 4.0.5).
> >>
> >> I've read some docs for setting this up including those just below as well 
> >> as a bunch of googling and reading through the list archive.
> >>
> >>http://www.ovirt.org/documentation/how-to/hosted-engine/
> >>
> >> http://www.ovirt.org/develop/release-management/features/heapplianceflow/
> >>
> >> http://www.ovirt.org/blog/2016/08/up-and-running-with-ovirt-4-0-and-gluster-storage/
> >>
> >> Every time I execute "hosted-engine --deploy" the process "hangs" when it 
> >> migrates the public IP address to a virtual nic interface. And in this 
> >> case, by "hang" I mean that I lose the connection to the server. I have no 
> >> idea if the process finishes or errors out.
> 
> Can you share logs at this point? Including /var/log/vdsm/* and
> /var/log/ovirt-hosted-engine-setup/* . If you have KVM access, you
> might manage to get them. Or copy after a reboot.
> Also please share your network configuration. Are you using
> NetworkManager (IIRC unsupported currently)? DHCP? Static IP conf?

I reinstalled the OS (wiping the logs) since my initial email. When/if it fails 
again I will provide the logs.


> 
> >>
> >> So obviously I'm doing something wrong.
> 
> Or it might be a bug.
> 
> >>
> >> I suspect that I need to take care of some network requirement before 
> >> starting. However, I can't find anything in the docs of how to prep the 
> >> server network environment before running "hosted-engine --deploy".
> >>
> >> Should probably also mention that some, if not all of the VMs will need a 
> >> public IP address. The physical server has a /29 to get started.
> >>
> > I have never setup such a server but if you create the ovirtmgmt bridge
> > first then the deploy will leave it alone and you won't lose network
> > connectivity.
> 
> See also [1]. Adding Dan (who wrote this). Best,
> 
> [1] https://bugzilla.redhat.com/show_bug.cgi?id=1301879#c1

Comments 4 in the link above mentions an "Installation Guide." Besides the 
"Quick Start Guide" and the links I initially reference I have not seen a 
"Installation Guide". Am I just missing it?

Thanks
Mark



> -- 
> Didi
> ___
> Users mailing list
> Users@ovirt.org
> http://lists.ovirt.org/mailman/listinfo/users

___
Users mailing list
Users@ovirt.org
http://lists.ovirt.org/mailman/listinfo/users


[ovirt-users] Self hosted single server network requirements

2016-11-18 Thread Mark Steckel
Hi folks,

I'm a complete OVirt newbie trying to set up a self hosted, single server and 
looking for some pointers to get going... (While new to OVirt, I'm long time 
sysadmin so not totally clueless.)

The server I'm using has a 4-core CPU, 64 GB of ram, and a pair of 500 GB SSDs 
set up with RAID 1 and running CentOS 7.2. (I do not have physical access to 
the server but can get KVM access when required.)

The goal is to set up this server as a self hosted, single server OVirt 
platform. Nothing mission critical, just want to be able to spin up VMs when 
needed and destroy them afterwards.

Trying to use OVirt 4.0.4 (now 4.0.5).

I've read some docs for setting this up including those just below as well as a 
bunch of googling and reading through the list archive.

   http://www.ovirt.org/documentation/how-to/hosted-engine/
   http://www.ovirt.org/develop/release-management/features/heapplianceflow/
   
http://www.ovirt.org/blog/2016/08/up-and-running-with-ovirt-4-0-and-gluster-storage/

Every time I execute "hosted-engine --deploy" the process "hangs" when it 
migrates the public IP address to a virtual nic interface. And in this case, by 
"hang" I mean that I lose the connection to the server. I have no idea if the 
process finishes or errors out.

So obviously I'm doing something wrong.

I suspect that I need to take care of some network requirement before starting. 
However, I can't find anything in the docs of how to prep the server network 
environment before running "hosted-engine --deploy". 

Should probably also mention that some, if not all of the VMs will need a 
public IP address. The physical server has a /29 to get started.

Any pointers would be greatly appreciated.

Thanks
Mark


___
Users mailing list
Users@ovirt.org
http://lists.ovirt.org/mailman/listinfo/users