[foreman-users] Hammer requires partidion-table even with image based VMs

[davide]

I'm trying to create a VM using an oVirt compute resource with Hammer, 
starting from an image, but it fails

Could not create the host:
  Error: At least one of options --partition-table, --partition-table-id is 
required
  
  See: 'hammer host create --help'

my command line is:


hammer host create \
--architecture-id=1 --domain-id=1 --operatingsystem-id=7 \
--hostgroup-title "Production" --name new-vm01 \
--provision-method image \
--image "CentOS_7.3" \
--compute-resource "oVirt" \
--compute-attributes 
"cluster=4df57363-2df7-45e6-b14c-1ac4537f6df8,cores=6,memory=68719476736,start=1"


If I add the '--partition-table-id=NNN' switch, then it works. Should I 
open a bug?

Thanks!

-- 
You received this message because you are subscribed to the Google Groups 
"Foreman users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to foreman-users+unsubscr...@googlegroups.com.
To post to this group, send email to foreman-users@googlegroups.com.
Visit this group at https://groups.google.com/group/foreman-users.
For more options, visit https://groups.google.com/d/optout.

[foreman-users] Re: Bare metal discovery: auto-provision NICs?

[davide]

On Tuesday, March 14, 2017 at 7:00:44 PM UTC+1, Brandon Boles wrote:

> https://github.com/bboles/foreman-nic-provisioning
>
> That script is pretty specific but may give you a starting point.  Let me 
> know if you have any questions.
>
>
Brandon, thanks for sharing. Anyway in the end I went another route: I 
pre-created the hosts in Foreamn programmatically using hammer CLI, since I 
already knew all the hosts being added.
I know that in a scenario "we are adding 200 machines at the same time" it 
doesn't scale as well as autodiscovery, but in my case they were just 20.  

-- 
You received this message because you are subscribed to the Google Groups 
"Foreman users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to foreman-users+unsubscr...@googlegroups.com.
To post to this group, send email to foreman-users@googlegroups.com.
Visit this group at https://groups.google.com/group/foreman-users.
For more options, visit https://groups.google.com/d/optout.

[foreman-users] Re: Bare metal discovery: auto-provision NICs?

[davide]

On Wednesday, March 8, 2017 at 10:47:30 AM UTC+1, Brandon Boles wrote:
>
> I have found that the best way is to just write a script to do the bonding 
> as part of provisioning.  Without the RFE that Lukas mentioned, setting up 
> bonds is painful at best.
>

Brandon, that's a really good idea! Even if I will probably come up with 
something tied to my infra, it's a good workaround.
Anyway, I'm going to upvote that RFE.

Thanks to both for you answers

-- 
You received this message because you are subscribed to the Google Groups 
"Foreman users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to foreman-users+unsubscr...@googlegroups.com.
To post to this group, send email to foreman-users@googlegroups.com.
Visit this group at https://groups.google.com/group/foreman-users.
For more options, visit https://groups.google.com/d/optout.

[foreman-users] Bare metal discovery: auto-provision NICs?

[davide]

Hello

is there a way with Foreman and the autodiscovery plugin to preconfigure 
NICs before provisioning the discovered bare metal server?
I want to provision directly with bonded interfaces and right now I've to 
do it manually, and I cannot find a way to control this with the 
autodiscovery plugin.
I'm using foreman 1.14.1

Thanks

-- 
You received this message because you are subscribed to the Google Groups 
"Foreman users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to foreman-users+unsubscr...@googlegroups.com.
To post to this group, send email to foreman-users@googlegroups.com.
Visit this group at https://groups.google.com/group/foreman-users.
For more options, visit https://groups.google.com/d/optout.

Re: [foreman-users] can katello be installed on an existing foreman installation?

[davide]

Hello

sorry for bumping this old thread but the issue still exists since 
http://projects.theforeman.org/issues/7605 is still not implemented.
So my question is: what's the "best practice" for a new Katello 
installation to be integrated as best as possible with an *existing* 
Foreman installation where I've already poured hours of configurations & 
tinkering?

Because right now I've installed (following the Katello manual) a fresh 
katello install on a brand new virtual machine and now I have a full 
foreman install with no data and knowing nothing about my already in place 
Foreman installation.

Thanks!

On Thursday, February 12, 2015 at 10:03:38 AM UTC+1, Cédric Dupont wrote:
>
> Hi,
>
> Thanks for the issue link.
> Here we have the same question. Using foreman since 2 years and happy. We 
> have get a look before at candlepin/pulp/katello but never make the step to 
> use them.
> Now that Katello is a plugin, we will be very happy to deploy them.
> So I understand it's needing time.
>
> To wait, can you give some advice/best practice if people want to start 
> using the candlepin and pulp product for exemple, so that later, we can 
> integrate all these beautiful products together when installing Katello ?
> For exemple : 
> can we start by installing candlepin/pulp and later these ones will just 
> need the installation of a capsule ?
> is there some good advice about what to avoid in configuration of Foreman 
> for later integration of katello plugin ? (thinking hostgroup, puppet 
> environnements ...)
>
> Thanks,
>
> Cédric
>
> 2015-02-08 21:28 GMT+01:00 Eric D Helms 
> :
>
>> Howdy,
>>
>> You cannot currently add Katello to an existing Foreman. Katello requires 
>> a stand-alone installation that provides itself and Foreman. This has been 
>> a popular request and as such is being tracked here - 
>> http://projects.theforeman.org/issues/7605
>>
>> Thanks,
>> Eric
>>
>> On Sun, Feb 8, 2015 at 3:14 PM, Cristian Falcas > > wrote:
>>
>>> Hello,
>>>
>>> Can Katelllo 2.1 be installed inside an existing foreman installation?
>>> I can't find anything to say that this is true.
>>>
>>> Best regards,
>>> Cristian Falcas
>>>
>>> --
>>> You received this message because you are subscribed to the Google 
>>> Groups "Foreman users" group.
>>> To unsubscribe from this group and stop receiving emails from it, send 
>>> an email to foreman-user...@googlegroups.com .
>>> To post to this group, send email to forema...@googlegroups.com 
>>> .
>>> Visit this group at http://groups.google.com/group/foreman-users.
>>> For more options, visit https://groups.google.com/d/optout.
>>>
>>
>> -- 
>> You received this message because you are subscribed to the Google Groups 
>> "Foreman users" group.
>> To unsubscribe from this group and stop receiving emails from it, send an 
>> email to foreman-user...@googlegroups.com .
>> To post to this group, send email to forema...@googlegroups.com 
>> .
>> Visit this group at http://groups.google.com/group/foreman-users.
>> For more options, visit https://groups.google.com/d/optout.
>>
>
>

-- 
You received this message because you are subscribed to the Google Groups 
"Foreman users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to foreman-users+unsubscr...@googlegroups.com.
To post to this group, send email to foreman-users@googlegroups.com.
Visit this group at https://groups.google.com/group/foreman-users.
For more options, visit https://groups.google.com/d/optout.

[foreman-users] Re: Hammer CLI, oVirt and templates

[davide]

On Tuesday, October 18, 2016 at 3:35:19 PM UTC+2, dav...@billymob.com wrote:
>
>
> Is this an Hammer bug? Has anyone got this working?
>
>
Solved. I have to specify in the Instance Type the 2-disks template, 
specifying only the image wasn't enough. I guess the confusion (at least 
for me) comes from the fact that oVirt UI has no clear distinction between 
"image" and "template", where Foreman clearly has. 

-- 
You received this message because you are subscribed to the Google Groups 
"Foreman users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to foreman-users+unsubscr...@googlegroups.com.
To post to this group, send email to foreman-users@googlegroups.com.
Visit this group at https://groups.google.com/group/foreman-users.
For more options, visit https://groups.google.com/d/optout.

[foreman-users] Hammer CLI, oVirt and templates

[davide]

Hello

I'm using Foreman 1.13 and oVirt 4.0.4 and I have an oVirt template with 2 
disks, both with data, from which I want to spin-up new VMs via Foreman.

If I create the VM from Foreman everything is correct, the 2 disks are the 
ones set in the oVirt template. But if I try from hammer CLI like this:

$ hammer host create --hostgroup-id=13 --compute-resource="My oVirt 
Resource" --provision-method="image" --image="MyImage" --name="test-01" 
--compute-attributes="start=1"  --operatingsystem-id=2 

Then, the new VM has only the "base" disk. And if I try like this

$ hammer host create --hostgroup-id=13 --compute-resource="My oVirt 
Resource" --provision-method="image" --image="MyImage" --name="test-01" 
--compute-attributes="start=1"  --operatingsystem-id=2 
--volume="size_gb=8,storage_domain=ba2bd397-9222-424d-aecc-eb652c0169d9,bootable=true"
  
--volume="size_gb=25,storage_domain=ba2bd397-9222-424d-aecc-eb652c0169d9,bootable=false"

Then 2 disks are created and attached but the second one (the 25GB disk) is 
a brand new disk and not a copy of the disk attached to the original 
template.

Is this an Hammer bug? Has anyone got this working?

Thanks in advance

-- 
Davide

-- 
You received this message because you are subscribed to the Google Groups 
"Foreman users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to foreman-users+unsubscr...@googlegroups.com.
To post to this group, send email to foreman-users@googlegroups.com.
Visit this group at https://groups.google.com/group/foreman-users.
For more options, visit https://groups.google.com/d/optout.

Re: [foreman-users] Provisioning - DBAN and Memtest

[davide]

On Saturday, October 1, 2016 at 11:33:54 AM UTC+2, Michael Hofer wrote:
>
>
>
> We use the "PXELinux default local boot" template to provide several live 
> systems and memtests. In addition there's a separate PXE template for each 
> operating system which takes care of booting the installer. This way we 
> don't 
> have to fiddle around with the build mode just to start a memtest. 
>
>
You're absolutely right, great tip! Thanks! 

-- 
You received this message because you are subscribed to the Google Groups 
"Foreman users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to foreman-users+unsubscr...@googlegroups.com.
To post to this group, send email to foreman-users@googlegroups.com.
Visit this group at https://groups.google.com/group/foreman-users.
For more options, visit https://groups.google.com/d/optout.

[foreman-users] Re: Serve more requests in parallel

[davide]

El lunes, 26 de septiembre de 2016, 23:38:45 (UTC+2), dav...@billymob.com 
escribió:
>
> Hello
>
> I'm using Foreman 1.12 and I've noticed that Foreman seems to permit just 
> one request at once. Is there some setting that I'm missing?
> I'm using apache2+passanger (installed with foreman-install and then 
> managed with Puppet)
>
>
Found it. I increased PassengerMaxPoolSize in passenger.conf to a value 
higher the PassengerMinInstances which I've increased to in boot 
05-foreman.conf and 05-foreman-ssl.conf 

-- 
You received this message because you are subscribed to the Google Groups 
"Foreman users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to foreman-users+unsubscr...@googlegroups.com.
To post to this group, send email to foreman-users@googlegroups.com.
Visit this group at https://groups.google.com/group/foreman-users.
For more options, visit https://groups.google.com/d/optout.