Re: [foreman-dev] Org with host deletion question

[Greg Sutcliffe]

On 8 June 2016 at 21:23, Tom McKay  wrote:

> To me, as a user, if I delete an org (or location) I'd simply want the
> foreman resources to be unassociated from it. It may be the case, for
> example, that a resource like a provisioning template is shared among
> multiple orgs. A host is different, I know, in that it can belong to only
> one org but I would still lean towards consistency by throwing it into the
> bucket of unassociated hosts.
>

I think that has to be the choice - whilst you *could* go to the edit
location page and unassign *every signle resource* from a bazillion tabs,
it very tedious, and ends up with the same result anyway. So long as we
document the behaviour clearly, then I think it's fine to just drop
associations

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

[foreman-dev] Re: Foreman Community Demo Items - Thu 09 Jun

[Greg Sutcliffe]

2 days to go, still no presenters - I see 153 closed bugs and 23 closed
features in the last 3 weeks, surely someone has something to say? :)

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

[foreman-dev] Strawpoll - Switching the community demo to a monthly timeframe

[Greg Sutcliffe]

Hi all

(apologies for cross-posting)

I'm thinking about ways to shake up the community demo slightly. It
occurred to me that the 3-week timeframe is somewhat odd if you don't know
the history of the team (i.e. that the full-time devs used to use
scrum/sprint methodologies, and the community demo grew out of the sprint
demo).

However, we no longer really do sprint in that way, and that takes some of
the constraints off the demo now. Moving to a monthly demo would make for a
more predictable schedule (say, first thursday of the month), and would
allow a larger period to generate useful/interesting features. This is
particularly relevant given the paucity of content over the last few demos
(although the timely merge of Dmitri's Puppet 4 proxy support saved me
yesterday :P). There's also the possibility to base the newsletter off the
demo, or vice versa, since both will be monthly.

The only potential downside I can see is contributors forgetting what they
worked on a month ago, or at least how to demo it, but that's not a huge
problem.

So what do you think? Is monthly better for you, or do you prefer the
3-weekly format? The poll is here:

https://gwmngilfen.typeform.com/to/hZRFE2

(credit to Daniel for bringing this site to my attention in his
Azure/HyperV poll - much better than the previous strawpoll I used!)
-- 
Greg
IRC: gwmngilfen

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

[foreman-dev] Re: Foreman Community Demo Items - Thu 28 Jul

[Greg Sutcliffe]

On 19 July 2016 at 11:20,  wrote:

> Hi all
>
> Demo time is upon us once again...
>

Reminder, this is *tomorrow*. So far we have ~20min of content (thanks lzap
and inecas), so I've still got plenty of space.

Thanks!
Greg

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

[foreman-dev] updates to test_develop_pull_request update subjobs

[Greg Sutcliffe]

Hi all,

Ori sent a pin to develop today[1] for the fast_gettext gem, however the
update17 subjob was still failing. Since these jobs are (I think) meant to
test db migrations on the currently supported versions, it seemed right to
update them to test against 1.11-stable and 1.12-stable.

So, I've updated the subjobs to be update111 and update112 repsectively.
However, update112 was still failing, as it also required the gem
pinning[2], so I've cherry-picked that commit. Update111 is fine because
the Gemfile in 1.11-stable already defines a lower version of
fast_gettext[3].

TL;DR test_develop_pull_request should be working again, but you may need
to kick the tests if you sent PRs in the last day or so.

[1]
https://github.com/theforeman/foreman/commit/46597839accd8533db119d56135a9b6ed9e01f87
[2] https://github.com/theforeman/foreman/blob/1.11-stable/Gemfile#L23
[3]https://github.com/theforeman/foreman/blob/1.12-stable/Gemfile#L21


-- 
Greg
IRC: gwmngilfen

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

[foreman-dev] Foreman Community Demo Items - Thu 28 Jul

[greg . sutcliffe]

Hi all

Slightly early this time, since I'll be in Nuremburg on Thurs :P

Demo time is upon us once again [1], so please start thinking and preparing
items that have been completed since the last demo on 28th Apr. There is a
query that will show you items completed (i.e. marked as closed) since the last
demo [2]. Please add demo items following the instructions on the agenda page 
[3].

I'd particularly like to have people who were present at the various birthday
events, for a quick panel segment on how that worked out.

If you can't be present but have something to show, add it to the agenda and
let me know - I'll be happy to talk about the feature in your absence. Please
do leave me enough time to familiarize myself with the feature though :)

[1] https://plus.google.com/events/ce6k42hdrovujq7qdhm6tbmjra8
[2] http://tinyurl.com/j62zsy9
[3] 
http://projects.theforeman.org/projects/foreman/wiki/Current_Sprint_Information

Cheers!
--
Greg
IRC: gwmngilfen

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

[foreman-dev] Foreman Community Demo Items - 7th July, 2pm BST

[Greg Sutcliffe]

Hi all

Birthday prep slowed me down, sorry this is late...

Demo time is upon us once again [1], so please start thinking and preparing
items that have been completed since the last demo on 28th Apr. There is a
query that will show you items completed (i.e. marked as closed) since the
last
demo [2]. Please add demo items following the instructions on the agenda
page [3].

If you can't be present but have something to show, add it to the agenda and
let me know - I'll be happy to talk about the feature in your absence.
Please
do leave me enough time to familiarize myself with the feature though :)

[1] https://plus.google.com/events/cupjll3uo0h26aqk89pa4bga5p0
[2] http://tinyurl.com/js33sek
[3]
http://projects.theforeman.org/projects/foreman/wiki/Current_Sprint_Information

Cheers!
--
Greg
IRC: gwmngilfen

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

Re: [foreman-dev] Revamping the news section of the website frontpage - design discussion

[Greg Sutcliffe]

There's lots of different opinions here - good, but takes time to work
through. For the birthday events, I'm running short on time, so I'm going
to send a new PR which is hopefully more broadly acceptable (an entry on
the front page and also in the news footer) while we work through the
longer-term revamp.

https://github.com/theforeman/theforeman.org/pull/656 if people want to
comment on that, otherwise lets keep wider discussion here ;)

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

Re: [foreman-dev] Deprecate EL6?

[Greg Sutcliffe]

On 8 August 2016 at 15:41, Ohad Levy  wrote:
>
> On Mon, Aug 8, 2016 at 5:33 PM, Eric D Helms  wrote:
>
>> This thread has seen a revival with many points being made on both sides.
>> However, things have gone cold for nearly a week now and there are
>> processes and decisions that hinge on the outcome with respect to users and
>> developers alike. Are we to assume that what has been done is done and this
>> discussion is moot? Some finality in this matter would be greatly
>> appreciated to either continue forward with EL6 builds and preparing all of
>> our ecosystem users for the 1.14 release to migrate or beginning now to
>> tell users they are SOL and to start testing transition and migration while
>> we work out and test the best way for them to do so.
>>
>
> I strongly prefer deprecating EL6 with Foreman 1.14, and would ask to
> revert the el6 changes in nighties.
>

I did ask previously to confirm if the cons to keeping EL6 were still as
simple as suggested on May 10th. I've heard no contradiction of that, so my
preference also goes to reverting the change in the nightlies.

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

[foreman-dev] From the demo - Plugin stats

[Greg Sutcliffe]

Hi all,

On yesterdays demo, Stephen asked if I'd share the plugin stats I've got,
so here they are. Bear in mind that:

* I've filtered out some things which are just dependency packages (eg
.*deface.*)
* I've merged the deb and rpm naming schemes into just "ruby..."
* I have no visibility of the Katello repos since they're not on yum.tf.o
* the usual caveats about mirrors, etc apply - don't take the numbers
seriously, just the ordering

$ bundle exec ruby packages/query_plugin_downloads.rb
# Plugin downloads: 2016-01-28..2016-07-28 (last 6 months)
NAME   | TOTAL
---|--
ruby-foreman-setup | 16501
ruby-foreman-tasks | 11613
ruby-dynflow   | 9761
ruby-foreman-docker| 9376
ruby-foreman-bootdisk  | 9147
ruby-foreman-discovery | 8178
ruby-foreman-hooks | 5998
ruby-smart-proxy-pulp  | 5766
ruby-puppetdb-foreman  | 5393
ruby-hammer-cli-foreman-tasks  | 5353
ruby-hammer-cli-foreman-boo... | 4783
ruby-foreman-templates | 4682
ruby-hammer-cli-foreman-docker | 4611
ruby-foreman-remote-execution  | 4574
ruby-foreman-xen   | 4345
ruby-foreman-salt  | 3937
ruby-foreman-cockpit   | 3717
ruby-foreman-digitalocean  | 3187
ruby-foreman-default-hostgroup | 2997
ruby-foreman-chef  | 2944
ruby-smart-proxy-salt  | 2739
ruby-bastion-devel | 2686
ruby-foreman-ansible   | 2652
ruby-foreman-dhcp-browser  | 2536
ruby-smart-proxy-discovery | 2313
ruby-diffy | 2304
ruby-ovirt-provision-plugin| 2231
ruby-less-rails| 2175
ruby-less  | 2173
ruby-foreman-openscap  | 2136
ruby-foreman-param-lookup  | 2111
ruby-git   | 2109
ruby-smart-proxy-remote-exe... | 2108
ruby-smart-proxy-dynflow   | 2092
ruby-foreman-abrt  | 1970
ruby-smart-proxy-abrt  | 1899
ruby-foreman-memcache  | 1883
ruby-hammer-cli-foreman-dis... | 1841
ruby-smart-proxy-openscap  | 1816
ruby-foreman-one   | 1655
ruby-smart-proxy-chef  | 1610
ruby-foreman-noenv | 1543
ruby-foreman-column-view   | 1538
ruby-foreman-expire-hosts  | 1430
ruby-foreman-custom-parameters | 1373
ruby-foreman-snapshot  | 1360
ruby-dalli | 1291
ruby-foreman-graphite  | 1282
ruby-hammer-cli-foreman-salt   | 1241
ruby-sequel| 1240
ruby-foreman-host-rundeck  | 1222
ruby-openscap  | 1191
ruby-foreman-mco   | 1172
ruby-opennebula| 1172
ruby-hammer-cli-foreman-rem... | 1160
ruby-foreman-reserve   | 1142
ruby-smart-proxy-dns-powerdns  | 1119
ruby-jgrep | 1074
ruby-ffi   | 1068
ruby-zscheduler| 1047
ruby-foreman-scap-client   | 1044
ruby-graphite-api  | 1043
ipxe-bootimgs  | 1011
ruby-newt  | 981
ruby-net-ssh-gateway   | 956
ruby-net-ssh-multi | 952
ruby-satyr | 920
ruby-smart-proxy-dns-route53   | 882
ruby-mysql2| 865
puppet-agent-oauth | 838
ruby-foreman-azure | 783
ruby-smart-proxy-discovery-... | 772
ruby-hammer-cli-foreman-ssh| 711
ruby-azure-core| 645
ruby-azure | 644
ruby-bootstrap-datepicker-r... | 633
ruby-safe-yaml | 590
ruby-chef-api  | 569
ruby-logify| 568
ruby-faraday-middleware| 493
ruby-fog-azure | 492
ruby-uuid  | 488
ruby-systemu   | 488
ruby-macaddr   | 486
ruby-little-plugger| 456
ruby-logging   | 398
ruby-foreman-simplify  | 380
ruby-scaptimony| 380
ruby-staypuft  | 355
ruby-ruby-hmac | 351
ruby-route53   | 344
ruby-foreman-openstack-cluster | 326
ruby-ftools| 314
ruby-open4 | 312
ruby-foreman-host-extra-val... | 283
ruby-foreman-dynflow   | 277
ruby-sprockets-rails   | 176
ruby-fast-gettext  | 172
ruby-builder   | 141

Much of the long tail appears to be dependencies I hadn't noticed :P

Have a good weekend!
Greg

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

Re: [foreman-dev] Revamping the news section of the website frontpage - design discussion

[Greg Sutcliffe]

On 30 June 2016 at 15:42, Dominic Cleal  wrote:

> That's fine, but there's far too much information shown in the
> screenshot. A handful of one to two line links should suffice so you can
> see and visit multiple items, rather than the whole summary or
> introduction from the latest item.
>

I agree in general, that was just a cut'n'paste to show layout - I like the
news and events sections, but I'd go for the last 5-10 blog entries (title
only, I think).

Only the frontpage is fine, especially if there are navigation links
> anyway to get through to news, events and whatever else is present on
> the site. Not everything needs to be on every page of the site.
>

Out of curiosity, let me invert that then - do you think there is ever a
situation that
would warrant such a banner?

On 1 July 2016 at 11:33, Daniel Lobato Garcia  wrote:

>
> Sorry, I think losing the whitespace (blue) we have, at the cost of
> moving the most important parts of the frontpage (description, 'get
> started'
> and 'learn more') isn't worth it. Also moving these things to the left
> looks worse
> IMO and make them seem less important.
>

Top banner (1 line at most) on top of every page? I think
> it'll be rather difficult, or impossible (not to mention slow) to keep
> everyone happy with this. If you can some designer to make your proposal
> of last news on the frontpage look good without making the main elements
> more important, I guess that'd work.
>

I'm a little unclear, sorry - are you saying that you're ok with moving
everything
on the white background to the /introduction page, it's just the
re-organisation
of the blue-background area that you have an issue with?

I do think I current frontpage needs something doing - if we haven't sold
people
enough for them to click on "Learn More" in the first screen, they probably
won't scroll down either.


> Honestly I'd prefer that (just one line!) for things like that, the
> yearly survey, releases, CVEs, critical events... I realize others will
> disagree.
>

Difficult discussion yeah - more voices please! :)

I do think  we need to be careful about how we use that, if it's too
frequent it
will really annoy everyone, or (worse) completely lose it's impact.

https://github.com/theforeman/foreman/pull/3400 would also work great
> and no one has to change the frontpage in that case :)
>

 Only for people who already have a Foreman install *and* have enabled
the widget. New users and users on secure sites still need to know :)

It'd be a pain to measure but there are certain actions we need
> from the community (testing RCs, filling the survey, upgrading, going to
> events...) that I think we'd get more input on if we had that in there.
>

Again, I do think we have to ration the use of such a banner - but such
metrics would be interesting to know if we could get them, I agree.

So 3 people, 3 different views. We're going to need more input here guys :)

Greg

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

[foreman-dev] Re: [event] Deep Dive on Webpack, today at 1pm UK time

[Greg Sutcliffe]

For those who missed it, the recording is at
https://www.youtube.com/watch?v=gNu1pZpOLIA

There's an issue with the screen sharing for a couple of minutes from 7
mins in, but we re-capped that section again at the end of the show (around
26:30) if you really want to see that.

Cheers!
--
Greg
IRC: gwmngilfen

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

[foreman-dev] Foreman Community Demo Items - Thu 25 Aug

[greg . sutcliffe]

Hi all

Astute observers will note that this should be *tomorrow* - however, as I was
on vacation, this 1-week reminder didn't go out. It seemed unfair to drop an
unannounced demo on everyone, so I've pushed it back a week. The new date is
25th August, usual time.

So, with that said, it's time to start thinking and preparing items that have
been completed since the last demo on 28th Apr. There is a query that will show
you items completed (i.e. marked as closed) since the last demo [2]. Please add
demo items following the instructions on the agenda page [3].

If you can't be present but have something to show, add it to the agenda and
let me know - I'll be happy to talk about the feature in your absence. Please
do leave me enough time to familiarize myself with the content though :)

[1] 
https://plus.google.com/b/102496134326414788199/events/c8ht5atvbgbabgul7jeino2vg4c
[2] http://tinyurl.com/jns3f5e
[3] 
http://projects.theforeman.org/projects/foreman/wiki/Current_Sprint_Information

Cheers!
--
Greg
IRC: gwmngilfen

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

[foreman-dev] Your input needed! Foreman Community Survey (2017 edition) is ready!

[Greg Sutcliffe]

Hi all

I'm happy to announce the 2017 community survey is now ready for your input! 
Tell us how you use Foreman, what's good/bad, and help us shape what the next 
year of Foreman looks like!

https://goo.gl/forms/xswoDALeJFoPMcy73

This year we've gone to a multi-page format - mainly for readability and 
sensible groupping. It shouldn't really take much longer to complete than last 
year.

However, to say thanks for giving us your input, we're going to be giving away 
some *prizes* in a raffle at the end of the survey! We're looking at getting a 
couple of RaspberryPi3 (or similar SoC devices) to give away, plus t-shirts & 
stickers to runners up. A chance to have your own Foreman sandbox for messing 
about on - so get responding!

https://goo.gl/forms/xswoDALeJFoPMcy73

I don't want to make this too burdensome, as we're an awesome & sensible 
community, but here's a minimum disclaimery stuff: 
* You'll have to give a contact email address at the end of the survey to be 
in the raffle, but it's entirely optional. You can remain anonymous if you 
prefer. All email addresses will be deleted after the raffle, in any case.
* If shipping/customs is tricky, I might have to give you a gift card for an 
equivalent amount. We'll work it out.
* Raffle will be done live on a future Communty Demo (prior notice be given) - 
email addressses will not be fully revealed (that would be a data breach!), 
but I'll show part of the address so it's clear that I'm not making it up :)

Thanks again for your participation in Foreman - I look forward to writing the 
analysis blog post in a month or so :)

Cheers
Greg
-- 
IRC / Twitter: gwmngilfen
Diaspora: gwmngil...@joindiaspora.com

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

[foreman-dev] Conference booths & manpower

[Greg Sutcliffe]

Hi all,

So I've had a few offers of help with the booth (thanks!), but it's not
generally available info. Time to fix that.

I've added a booth-duty section to the top of the speakers pad[1] (which I
totally need to clean up once this is all over :P). I don't want to make
this majorly formal, but if you want to note down times you will (or won't)
be able to handle booth duty, we'll have a clearer picture of the situation.

I do have quite a few talks this year, so I can't be there the whole time.
Ensuring those times, at least, are covered would be great.

[1] http://pad-katello.rhcloud.com/p/foreman-speakers

Cheers,
Greg

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

Re: [foreman-dev] RFC idea: Templates rendering only through Proxies

[Greg Sutcliffe]

I'll comment on the rest of this when I have time to think it over, however I 
do want to correct one point:

On Thursday, 26 January 2017 10:27:47 CET Lukas Zapletal wrote:

> This is only relevant to provision, iPXE and script templates, all the
> others are not affected by this. PXE templates already works this way,
> finish and user_data are injected via ssh/cloudinit. 

Not true. Finish scripts are used by preseed (Debian/Ubuntu) for the PXE-based 
provisioning process, and there were some discussions around moving the 
kickstart to doing the same for parity (i.e. calling the finish template from 
%post). You'll need to therefore account for the differing use of finish 
templates depending on provision method.

Greg
-- 
Greg Sutcliffe, Foreman Community Lead
IRC / Twitter: gwmngilfen
Diaspora: gwmngil...@joindiaspora.com

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


signature.asc
Description: This is a digitally signed message part.

Re: [foreman-dev] Re: Draft community survey questions

[Greg Sutcliffe]

On Friday, 20 January 2017 15:51:28 GMT Stephen Benjamin wrote:
> Also "Smart proxy, Hammer & API" page - I think maybe adding "Katello"
> in parens next to smart_proxy_pulp might help people know what it's
> for. I doubt most Katello users are aware of the plugin name on the
> smart proxy side.

Good point, done.
 
> On Fri, Jan 20, 2017 at 3:49 PM, Stephen Benjamin  
wrote:
> > The 1 to 5 selectors don't seem to be working correctly, it's not a
> > preference order right?

Yes, stupid mistake. Thanks!
 
On Sunday, 22 January 2017 19:04:58 GMT Michael Hrivnak wrote:
> As a content person, I'm interested in what Katello users are doing in that
> area. Some ideas that could be valuable to know:

I did think about Katello input, but cut it in the first round due to survey 
length. Now that we're multi-page, I think it's fine to include. Thanks for 
reminding me :)

I've restructured it so that it's more generally applicable to people who 
manage content in other ways (for example, I manage Puppet with puppet-
librarian and DEBs with Aptly). My aim is to answer your questions about the 
content we do support, but also to try and gain some more understanding about 
areas we could look to including in future work.

This really needs to go out today so the initial rush can ebb a little before 
DevConf, where we'll push it again (and again a week later). I've filled it 
out once myself to test the questions this time... (oops :P) and unless 
anything major comes up, I'll wipe the replies and publish the survey to the 
users-list later on tonight. 

Cheers for the input guys!
Greg

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

Re: [foreman-dev] Draft community survey questions

[Greg Sutcliffe]

Ok, the Google Form is done - I've added one or two more good suggestions I 
got privately (thanks Ewoud and Dmitri :P). The link is:

https://goo.gl/forms/i5Gu2o31vbuQLToh1

I consider this to be a "beta" - have a play with it, but expect the responses 
to be wiped before we announce it as "live". If no-one has any major concerns, 
then I'll announce it early next week.

Greg

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

Re: [foreman-dev] Draft community survey questions

[Greg Sutcliffe]

On Friday, 20 January 2017 06:45:16 GMT Duncan Innes wrote:
> On page 4, I can only select one Compute Resource when question asks
> "select all that apply".  Same for selecting which features I use on my
> Smart Proxies and which Smart Proxy plugins I use on page 5.
> 
> Should't these three inputs be checkboxes instead of radio buttons?

You are correct - the dangers of cut'n'paste. Should be fixed now, thanks!

Greg

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


signature.asc
Description: This is a digitally signed message part.

[foreman-dev] cosmetic yumrepo issue in foreman-infra causing large amount of cron mail

[Greg Sutcliffe]

I'm getting a lot of mails from the slaves at the moment like the one below. 
I'm not super-familiar with the 'yumrepo' puppet resource, but does it just 
need a 'name' parameter added to this block?

https://github.com/theforeman/foreman-infra/blob/master/puppet/modules/slave/
manifests/init.pp#L226

Or is it more than that? Happy to send a trivial PR if thats all it is.

Greg

--  Forwarded Message  --

Subject: Cron  run-parts /etc/cron.hourly
Date: Thursday, 19 January 2017, 16:14:35 GMT
From: (Cron Daemon) 
To: r...@slave02.rackspace.theforeman.org

/etc/cron.hourly/0yum-hourly.cron:

Repository 'isimluk-openscap' is missing name in configuration, using id

-

--
IRC / Twitter: gwmngilfen
Diaspora: gwmngil...@joindiaspora.com

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

Re: [foreman-dev] cosmetic yumrepo issue in foreman-infra causing large amount of cron mail

[Greg Sutcliffe]

On Thursday, 19 January 2017 16:45:00 GMT Ewoud Kohl van Wijngaarden wrote:
> Pretty sure adding a name should be all. I'd recommend the same as the ID
> now to prevent duplicate resources

Thanks, https://github.com/theforeman/foreman-infra/pull/271 submitted.

Greg

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

[foreman-dev] Re: New major release of foreman_templates - info for other plugin authors

[Greg Sutcliffe]

Foreman_templates 3.0.0 went out today, which contains this option. You can
see an example implementation in my PR to Remote Execution [1].

I've done an early .0 release as we go into code-freeze for 1.13 so I can
iron out bugs. Testing / feedback is very welcome ;)

[1] https://github.com/theforeman/foreman_remote_execution/pull/202

Cheers
Greg

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

[foreman-dev] Foreman Community Demo Items - Thu 15 Sep 3pm [GMT+1]

[greg . sutcliffe]

Hi all

Once again, it's time to start thinking and preparing items that have
been completed since the last demo on 28th Apr. There is a query that will show
you items completed (i.e. marked as closed) since the last demo [2]. Please add
demo items following the instructions on the agenda page [3].

This month we'll be moving to YouTube Live, since Google has deprecated the old
way of doing things. I've given it a quick test, and as far as I can tell, it's
still using Google Hangouts on Air under th hood, so presenters should see no
differences. Do bear with me if there are any technical issues on this first
proper use of the new platform :)

It's also pushed back one hour (15:00 UK time), so watch out for that. The
Foreman calendar has the right entry, if you want to grab the ICS file.

If you can't be present but have something to show, add it to the agenda and
let me know - I'll be happy to talk about the feature in your absence. Please
do leave me enough time to familiarize myself with the content though :)

[1] https://www.youtube.com/watch?v=GFNPHypFhl4
[2] http://tinyurl.com/gpxklj6
[3] 
http://projects.theforeman.org/projects/foreman/wiki/Current_Sprint_Information

Cheers!
--
Greg
IRC: gwmngilfen

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

Re: [foreman-dev] Re: Automate IP allocation over specifying subnets in machine creation

[Greg Sutcliffe]

On 31 August 2016 at 11:45, Lukas Zapletal  wrote:

> > BTW I also tried to work with the API of "Free IP" but couldn't managed
> to
> > authenticate properly, can you give me an example of how to use it?
> > that way we could use the workaround I spoke of before...
>
> The proxy API directly? That's not possible, unless you use HTTP client
> certificate. Sign it with your puppet ca and use it if you want.
>

Well, it is possible - but you have to make some changes to the proxy :)

The proxy, by default, sets:

:trusted_hosts:
  - foreman.domain.org

This means 2 things - one, API calls need to be wrapped with a certificate
signed by the proxy's CA, and 2, the cert's name has to be in the
trusted_hosts.

So, you have three options, from most to least-secure:

1) If only a few machines will need to call the free_ip endpoint, you can
generate new certs from the same CA, give them to the clients, and add them
to trusted_hosts (i.e what Lukas said)
2) disable trusted_hosts entirely, at which point any valid SSL request can
access the API
3) Allow non-ssl requests to that proxy module

Hope that helps!
Greg

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

[foreman-dev] Re: Foreman Community Demo Items - Thu 25 Aug

[Greg Sutcliffe]

Reminder, this will be in two days - as of now, we have just 2 presenters,
so plenty of room for more :)

Greg

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

[foreman-dev] [Event] Foreman Deep Dive - Host Facets with Shimon Shtein - 10th Oct 2pm GMT+1

[Greg Sutcliffe]

Hi all,

(apologies for cross-posting, this is relevant to both lists)

The next entry in the Foreman Deep Dive series will be next week, 10th Oct,
2pm UK time. In this episode, Shimon Shtein (shimshtein on IRC) will be
giving us a breakdown of the Host Facets system that's been added to the
core codebase - what it's for, the principles behind it, and how you can
use it yourself.

As ever, join us live for Q or hop in the channel to ask questions later.

Cheers!
-- 
Greg
IRC: gwmngilfen

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

Re: [foreman-dev] Foreman Hooks Collaboration

[Greg Sutcliffe]

On 10 October 2016 at 16:19, Sean O'Keeffe  wrote:

> Hi Guys,
>
> So I wanted to get people opinions on having a central repo to collaborate
> around foreman_hooks? It could be kind of similar to community_templates
> but for foreman_hooks, but hopefully it could also be a good source for
> ideas for new plugins.
>

Sounds excellent. Does it make sense to host those in commuity_templates
itself (either a subdir or a separate branch)?

Greg

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

[foreman-dev] Re: [Event] FOSDEM 2017 & CfgMgmtCamp Ghent - call for papers

[Greg Sutcliffe]

Don't forget to get your submissions in! DevConf closes tomorrow and FOSDEM
& CfgMgmt close next week. We really want to hear from users as well as
devs - and if you're *at all* unsure about *anything* (the topic, the
submission process, speaking in general :P) then feel free to contact me
directly and I'll help you out.

I've wrapped up our call to action along with a repeat of the CFP links in
a quick blog post -
https://theforeman.org/2016/11/tell-us-your-story-at-cfgmgmtcamp-ghent.html

Thanks!
Greg

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

Re: [foreman-dev] Re: High Availability - best practices docs group

[Greg Sutcliffe]

On 25 October 2016 at 13:53, Christopher Pisano  wrote:

> we should maybe all try and jump on a video call and talk out our
> different experiences and come together as to what we believe *should* be
> the best practices.
>

That sounds like a good idea - I can host that if needed (but you could
probably figure out a hangout yourselves :P). Would you want that public
(recorded, deep-dive style), or "private" (jn the sense that its open to
the community to join, but not recorded)?

Greg

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

Re: [foreman-dev] Adding a community tools/extras/utils repository

[Greg Sutcliffe]

On 24 October 2016 at 19:59, Eric D Helms  wrote:

> I'd like to add a new repository focused on providing space for community
> members to contribute tools and scripts that they write. I think this would
> provide a number of benefits:
>
>  * allow users a place to contribute to the community with custom code
> they write
>  * provide a centralized place for users to find useful tools and scripts
> that other users have written that may solve their problem
>  * inform developers to the types of problems users are solving through
> custom scripts to better inform application design and features
>

+1 from me, this sounds like an excellent way to share knowledge, similar
to how we've seen collaboration grow in the community-templates repo. Some
promotion is probably in order once the repo is up and running, perhaps a
blog post inviting contribution?

I'd propose the following:
>
>  * create 'community-tools' or 'community-extras' or 'community-utils'
> repository (foreman-tools and foreman-extras sound like plugins given our
> conventions)
>

+1 to "community-extras" - given we already have "community-templates" this
seems in keeping.

 * add tools and scripts underneath a folder for each
>  * start the repository with a core set of developers to help manage it
> and merge code for users
>
> A starter script would be [1] which might be useful for Python developers
> and does not get much exposure sitting out on the site like it does today.
>
> [1] http://www.katello.org/community/scripts/upload_file.py
>

Another few things which leap to mind are:

* Foreman-hooks scripts - I've heard of people doing all sorts of stuff
with this
* Discovery image customizations - e.g. rack-management integration from
one of the case studies

Greg

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

[foreman-dev] [RFC] Compute Resources as Plugins

[Greg Sutcliffe]

Hi all,

TL;DR I just opened an RFC[1] for moving Compute Resources from core to
plugins. Opinions wanted

In the last few weeks I've been talking to a variety of people who've had
some interest in specific compute resources - I've talked about AWS, GCE,
and OpenStack in the last week alone. In most cases, there's a desire to
improve how Foreman interacts with these services, but there's quite a high
barrier to entry.

For some time we've had the option to deploy Compute Resources as plugins.
I believe it may be time to look at moving some of the core CRs out to
plugins, and see if we can gather community interest in picking up and
maintaining the resulting plugin repo. I'll certainly be pointing peole at
this thread and the RFC to add their thoughts.

The RFC[1] is a great place to discuss the implementation plan
(particularly if I missed anything), but I also wanted a thread to discuss
who might be interested in helping to take these projects on. So, have at
it :)

[1] https://github.com/theforeman/rfcs/pull/28

Cheers
-- 
Greg
IRC: gwmngilfen

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

[foreman-dev] [event] CfgMgmtCamp tickets now available (& CFPs still open!)

[Greg Sutcliffe]

Hi all,

If you're thinking of joining us at CfgMgmtCamp in February, be aware that
the tickets are now available and going fast - you can get them at
http://cfgmgmtcamp.eu/

Also, the CFPs for both CfgMgmtCamp & FOSDEM are still open until the end
of Friday, so do consider submitting a talk to tell us about your
experiences/uses/development/plugins/etc of Foreman - we'd love to hear it!
http://cfgmgmtcamp.eu/#contributions

Cheers
Greg
-- 
Greg
IRC: gwmngilfen

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

[foreman-dev] [Event] Deep Dive - React / JS / UI - 11.30 GMT Wed 2nd Nov

[Greg Sutcliffe]

Hi all,

Next week, 2nd Nov, 11.30am GMT, Ohad and Gail will hold a deep dive into
the React and JS updates to Foreman core. We will have a very basic
introduction to ReactJS [1] and how it is currently used in Foreman, as
well as a wider discussion about the Foreman UI and where it could be
heading.

Come to this deep dive if you are interested in:
* UX improvement in Foreman
* JavaScript / client side future of Foreman
* want to understand what React is

As ever, questions and feedback will be welcome during the show, either on
IRC (#theforeman ) or via
the YouTube Live chat.

Cheers
-- 
Greg
IRC: gwmngilfen

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

Re: [foreman-dev] Use mention-bot to increase reviews?

[Greg Sutcliffe]

On 27 October 2016 at 14:55, Ohad Levy <ohadl...@gmail.com> wrote:

>
> On Mon, Oct 17, 2016 at 4:02 PM, Greg Sutcliffe <greg.sutcli...@gmail.com>
> wrote:
>
>> On 13 October 2016 at 13:28, Eric D Helms <ericdhe...@gmail.com> wrote:
>>
>>> This has been turned on for the Katello repo, if devs find it needs
>>> tweaking there is a configuration file that can be added (
>>> https://github.com/facebook/mention-bot#configuration).
>>>
>>
>> How's that going for you?
>>
>> Dominic or Ohad, could you turn it on for the other repos mentioned, as a
>> trial? Thanks!
>>
>
> Done.
>

Thanks. It's already pinged me for a review, so that was cool.

Lets see how it goes for a few weeks and we can see if we want to expand to
other repos. Feedback welcome as we go :)

Greg

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

[foreman-dev] Re: [Event] Foreman Community Demo Items - Thu 13 Oct 3pm [GMT+1]

[Greg Sutcliffe]

Just a reminder that the demo will be today, in a few hours. Still time to
get on the agenda if you wish (although it's looking pretty good, ty guys!)
- I'll be making up the slide deck in an hour or so.

Greg

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

Re: [foreman-dev] Use mention-bot to increase reviews?

[Greg Sutcliffe]

On 12 October 2016 at 16:29, Lukas Zapletal  wrote:

> > Sounds positive so far - which repos should we try it on? I'm thinking
> > core, proxy, katello and the website for now? We can put it everywhere if
> > that goes well.
>
> I love this bot, I already know that in advance.
>
> I'd scratch the website tho, the three would be a good start.
>

I put the website because quite a few new contributors start there, with
small doc fixes - thus it has a higher number of people for the bot to
ping. Might be interesting to see it's heuristics in action. But I don't
mind either way :)

Greg

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

Re: [foreman-dev] Use mention-bot to increase reviews?

[Greg Sutcliffe]

On 13 October 2016 at 13:28, Eric D Helms  wrote:

> This has been turned on for the Katello repo, if devs find it needs
> tweaking there is a configuration file that can be added (
> https://github.com/facebook/mention-bot#configuration).
>

How's that going for you?

Dominic or Ohad, could you turn it on for the other repos mentioned, as a
trial? Thanks!

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

[foreman-dev] [Event] FOSDEM 2017 & CfgMgmtCamp Ghent - call for papers

[Greg Sutcliffe]

Hi all

Firstly, apologies for the cross-post - both user stories and development
talks are welcome for these CFPs, so it's relevant to both lists.

# FOSDEM - 4 & 5th Feb 2017

The call-for-papers for FOSDEM 17 is now available. As with previous years,
there's both a Configuration Management track and a Virtualization track -
various things from the Foreman community might be relevant in either
track. You can find the CFPs at:

CfgMgmt: https://lists.fosdem.org/pipermail/fosdem/2016-October/002459.html
Virt/IaaS: http://www.ovirt.org/blog/2016/10/call-for-proposal-fosdem-2017/

Should you wish to submit to other rooms, the full list is at:
https://fosdem.org/2017/news/2016-10-10-accepted-developer-rooms/

Submissions are due by Nov 18th

# CfgMgmtCamp Ghent - 6th & 7th Feb 2017

CfgMgmtCamp is happening again in Ghent this year, and we're delighted to
be a part of it again - and the CFP is now open! This year we're going for
"tags" on the submissions, and we'll build the tracks out of the popular
tags - so be sure to tick Foreman when submitting :)

https://docs.google.com/forms/d/e/1FAIpQLSeAMyDhrz4Z-xcSvCIroDoA1EKy-FhWIRwg8CEwjB1Lt9GM_g/viewform?c=0=1

Submissions are due by Nov 15th

Looking forward to seeing you all there!
Greg
-- 
Greg Sutcliffe
IRC: gwmngilfen

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

[foreman-dev] [Event] Foreman Community Demo Items - Thu 15 Dec 2pm [GMT]

[greg . sutcliffe]

Hi all

Time for the last demo of the year! In this demo I'll be happy to accept anyone
who'd like to come and spend a few minutes talking about theirfavourite
features/patches/moments of 2016 - I'll certainly be preparing a list of my own
:)

We'll also be covering the usual demos of items which have been completed since
the last demo on 2016-11-24. There is a query that will show you items
completed (i.e. marked as closed) since the last demo [2]. Please add demo
items following the instructions on the agenda page [3].

If you can't be present but have something to show, add it to the agenda and
let me know - I'll be happy to talk about the feature in your absence. Please
do leave me enough time to familiarize myself with the content though :)

Please note this demo is using the *old* time of 2pm due to a schedule conflict
at 3pm. This also means we have a hard cap of one hour, so I'll be more strict
with time if it's a busy demo

[1] https://www.youtube.com/watch?v=CY1U_54Cbbs
[2] http://tinyurl.com/jpbk9tm
[3] 
http://projects.theforeman.org/projects/foreman/wiki/Current_Sprint_Information

Cheers!
--
Greg
IRC: gwmngilfen

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

Re: [foreman-dev] Nominating Katello.org devs for theforeman/theforeman.org commit access

[Greg Sutcliffe]

+1

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

[foreman-dev] Re: [Event] Foreman Community Demo Items - Thu 15 Dec 2pm [GMT]

[Greg Sutcliffe]

Reminder that this is tomorrow and we currently have *no* entries on the
agenda. Surely someone wants to talk about something new or something from
the year-in-review ;)

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

[foreman-dev] [event] Foreman Construction hackday - Ghent, 8th Feb 2017 (after CfgMgmt) - Registration open!

[Greg Sutcliffe]

Hi all,

As promised on yesterday's demo, the registration page for the Foreman 
Construction Day is now open! This went really well last year (20+ 
people, all of whom enjoyed it), so I'm excited to see if we can do even 
better. You can register here:


http://foreman-construction-day-2017.eventbrite.com

The feedback last year was to perhaps have a little more structure, and 
maybe some prior discussion of topics. So, this year, we're adding a 
half-day track of deep dives and workshops. The exact agenda is still to 
be decided, but the current proposal is:


* 09.30 - Welcome & Introductions
* 10.00 - Deep dive / workshop 1
* 10.30 - Deep dive / workshop 2
* 11.00 - coffee break
* 11.30 - Deep dive / workshop 3
* 12.00 - Deep dive / workshop 4
* 12.40 - LUNCH
* Afternoon - Coding time (with coffee break at 15.00)
* 16.00 - Conclusions & Thanks

As with last year, we'll have several rooms, so if you want to grab some 
people and go code all morning, that's still an option, and we'll have 
coding time all afternoon too. I expect by lunchtime we'll all have an 
idea of what we'd like to spend the afternoon on :)


However, I'd like input from the community on what these sessions & 
hacking topics should be! So far, from speaking to a few people, I know 
we could do workshops on:


* Getting started with contributing (dev environment, writing good 
bugs/PRs, getting help)

* Running Foreman via docker-compose
* Developing Foreman UI components with React
* Getting started with Foreman plugins

I'm sure there's many other potential topics, so I've created a really 
short (two questions!) form here:


https://goo.gl/forms/phjwj2ViQKn1s9kZ2

Feel free to put multiple topics in one answer, or submit the form 
multiple times - I'll parse it all out later :)


Any questions, let me know. Hope to see you there!

Cheers
Greg
--
IRC / Twitter: gwmngilfen

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

Re: [foreman-dev] Draft community survey questions

[Greg Sutcliffe]

Thanks all, and sorry for the delay. Some inline comments and the final 
draft attached separately :P


Ori Rabin wrote:
Maybe the question: How would you rate our user support? can have links 
instead of bringing back the do you know our IRC question?


I like that, added.

Tomas Strachota wrote:

+1 for the raffle. It motivates you to respond even on the last day of

the survey.

Good point.


How about raffle for the foreman t-shirts? Or is it too

common and everybody already has one from conferences?

They (and stickers) are what we give out for free, and seems somewhat 
stingy :)


I have a budget for a couple of decent items, 2 or 3 depending on price. 
The question is what? It needs to be something available in multiple 
countries (because that is likely cheaper than shipping from elsewhere), 
a nice thing to win, and relevant to us. My current thinking is 
something like a RaspberyyPi3 / oDroid / etc for running your own ARM 
Foreman server on :P - thoughts?


Neil Hanlon wrote:
+1 for raffle and contributor survey. (I don't have a t-shirt... 
Yet...)


Let me fix that for you - ping me an address and size :)


In general, it's been my experience that people who are going
to complete surveys will complete them regardless of length. By
that I mean most people won't be swayed into doing a survey because
it's short unless they already planned on completing it going in.
I know everyone is busy, but 15 minutes for something most users 
probably

use multiple times a day isn't really that much to ask.


That's a great point. I've converted the draft to a multi-page format, 
and tidied up the group to something which I hope is logical. It's also 
enabled me to re-add many of the things I dropped due to trying to be 
brief.


Ohad Levy wrote:
can we take back the input from Shlomi's tread about what people are 
annoyed by, break it into categories, and have a question


Originally I wanted to leave this as an open text field ("what needs 
fixing?") but I think we can combine it. I've added a few suggestions 
from the thread and an Other box too.


Eric D Helms wrote:

Some question in line below. Could we add some questions around smart
proxies? I don't know that I have any idea about:


Great point. Page added for Proxies, and since it's short I put the 
Hammer and API questions there too.



The plugin question would cover which configuration management project
users use, but it wouldn't indicate Puppet usage and Puppet 3 vs
Puppet 4 usage in our ecosystem. A question around those two might be
useful.


I added just one, but if there's more sing out.

+! to splitting out the OS distros into versions (e.g. RHEL6, RHEL7,
Fedora 24, CentOS 6, Debian Jessie) as that gives us a better idea of
where to focus and may help some plugins decide on what they want to
focus their support on.


Done.


Would it be worth asking an open ended question about what users pain
points are? I suppose the foreman-users post did this but still might
be worth it in the official survey.


Added as part of the final "What else would you like add?" question to 
highlight pain points are definitely worth mentioning.



Something to consider to help Katello developers would be a question
around how many users do not currently manage content but plan to in
the future. You could perhaps ask this more broadly about plugins that
users plan to add to their environments.


That's a good question. The plugin page is already huge, so I wonder if 
it makes more sense in the "wrap-up" section? For now, I've added an 
open question to the main first page.



Do you Use Locations / Organization features?


Why drop this question? Given how hotly some developers discuss this,
I think this is valuable data.


I don't think there's anything new here. We gathered good feedback which 
(to me) confirmed that moving to a tag-based system wouldn't break many 
(if any) setups. Simply asking the same broad question again won't 
extend that, I don't think - but if you've got something more specific 
you'd like to ask, I can add it.


I'm mocking this up in Google Forms at the moment, but the markdown is 
attached. I'll publish next week if there are no major concerns :)


Gre
--
IRC / Twitter: gwmngilfen
Diaspora: gwmngil...@joindiaspora.com

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

## Page 1 - Foreman Core & Support

How long have you been using Foreman?
* 3 months
* 6 months
* 1 year
* 2 years
* 3+ years

How many people use Foreman in your organization
* 1-4
* 5-9
* 10-49
* 50+

What Foreman version are you using?
* nightly
* 1.14
* 1.13
* 1.12
* older

How many nodes do you manage with Foreman?
* 0-9
* 10-49
* 50-199
* 200-499
* 500-999
* 1000-
* 1-1
* 2+

What operating system 

[foreman-dev] [Event] Foreman Community Demo Items - Thu 19 Jan 3pm [GMT]

[greg . sutcliffe]

Hi all

First demo of the year! I see Marek and others have been busy pre-filling the
agenda, so thanks for that (and thats always fine, if anyone else wants to get
into the habit :p). For everyone else, have a think for items which have been
completed since the last demo on 2016-12-15. There is a query that will
show you items completed (i.e. marked as closed) since the last demo [2].
Please add demo items following the instructions on the agenda page [3].

If you can't be present but have something to show, add it to the agenda and
let me know - I'll be happy to talk about the feature in your absence. Please
do leave me enough time to familiarize myself with the content though :)

[1] https://www.youtube.com/watch?v=WwY_IawhRKct
[2] http://tinyurl.com/zvmf3a4
[3] 
http://projects.theforeman.org/projects/foreman/wiki/Current_Sprint_Information

Cheers!
--
Greg
IRC: gwmngilfen

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

Re: [foreman-dev] Finish and cloud-init script support

[Greg Sutcliffe]

On Tuesday, 28 March 2017 12:35:41 BST Neil Hanlon wrote:
> Is there any guide/page on writing a compute resource plugin that supports
> cloud init? I'm contemplating working with xen-orchestra, and writing a
> plugin to interface with that (as it provides cloudinit for xenserver)

IIRC we just fire it at Fog at then let Fog handle it, there's very little on 
our side. The assumption is that user-data will do a phone home, so there's 
really little more to do than render a template and add it to the cerate_vm 
hash. I can look up code examples if it helps ;)

Greg

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

[foreman-dev] [Event] Foreman Community Demo Items - Thu 30 Mar 3pm [GMT]

[greg . sutcliffe]

Hi all

Demo time! As always, have a think for items which have been completed since
the last demo on 2017-03-09. There is a query that will show you items
completed (i.e. marked as closed) since the last demo [2].  Please add demo
items following the instructions on the agenda page [3].

If you can't be present but have something to show, add it to the agenda and
let me know - I'll be happy to talk about the feature in your absence. Please
do leave me enough time to familiarize myself with the content though :)

[1] https://www.youtube.com/watch?v=QfANwMzxebE
[2] http://tinyurl.com/l2b7vgn
[3] 
http://projects.theforeman.org/projects/foreman/wiki/Current_Sprint_Information

Cheers!
--
Greg
IRC: gwmngilfen

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

Re: [foreman-dev] Ansible based foreman-installer

[Greg Sutcliffe]

On Tuesday, 14 March 2017 18:16:59 GMT Michael Hofer wrote:
> Hi Ohad
> 
> On Tue, 14 Mar 2017 08:45:19 +0200
> Ohad Levy  wrote:
> [...]
> 
> > Would you be interested in doing a deep dive about the installer? what it
> > currently does, how to use it etc?
> > 
> > I think it would be interesting to our increasing ansible users community.
> 
> [...]
> 
> Sure, why not! :)
> 
> Would that be a topic for a community demo?

We can do it either way (or both!). Community demo items tend to be short 
(5-10 mins tops) and stay at a high level. Deep dives obviously have more time 
to get into the details.

I'd suggest a dedicated deep dive to start with, and then you'll always be 
welcome to join the regular demos to show off latest developments in the 
Ansible installer.

If that works for you, I'll ping you offlist to sort out a date & time for the 
deep dive.

Greg
-- 
IRC / Twitter: gwmngilfen
Diaspora: gwmngil...@joindiaspora.com

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


signature.asc
Description: This is a digitally signed message part.

Re: [foreman-dev] Link to redmine issues using prprocessor

[Greg Sutcliffe]

Will do :)

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

Re: [foreman-dev] Link to redmine issues using prprocessor

[Greg Sutcliffe]

While we're talking about modifying PrProcessor, some of the automatic
and requested task options in the MIQ bot are pretty cool - maybe we
should steal^W copy those in? :P. I can definitely see uses for
add/remove labels, at least.

https://github.com/ManageIQ/miq_bot?#automatic-tasks

Greg
-- 
IRC / Twitter: @gwmngilfen
Diaspora: gwmngil...@joindiaspora.com

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

[foreman-dev] Re: [Event] Foreman Community Demo Items - Thu 13 Apr 3pm [GMT]

[Greg Sutcliffe]

Please disregard, this got sent by accident before I updated the dates. The 
correct thread is at 
https://groups.google.com/d/topic/foreman-dev/ylQq-hPbzjQ/discussion

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

Re: [foreman-dev] Unify date format in Foreman and plugins

[Greg Sutcliffe]

+1 for consistency, further comments below ;)

On Thu, 2017-04-13 at 10:05 +0200, Marek Hulán wrote:
> > > On the reports (where you see multiple) then I think the "ago"
> > > format isn't useful because the granularity is too low so it's
> > > hard to compare. IMHO in a list they should all have the same
> > > format. On a host page where you see "Last report: 1 hour ago" it
> > > does make sense. I hope that clarifies it.

+1 to the fact that it doesn't always make sense to use "ago".

> > I totally agree. Let's not drop the "time ago in words" format
> > entirely.
> 
> Right, there are places where it makes sense. How about there was
> always a tooltip so when you hover over "ago" it would display
> timestamp and vice versa?

+1 to the fact that it does *sometimes* make sense :)

I think it makes sense to separate "absolute time" from "relative
time". Each of those things has it's use, as has already been said -
absolute time is usually better in lists, relative time is usually
better in information on an object (although there will be exceptions
to these rules, of course).

Perhaps we should accept that these two things need to exist, and
define a consistent format for both?

> Second thing is what the format of timestamp there (and everywhere
> where we use it) should be. And that's something I'd like to unify
> everywhere including plugins. Maybe the core should provide a helper
> that plugins should use to format the date.

+1 for a helper for each of these two objects. Then we can use them
where needed, for example (warning, bad psuedocode ahead):

Report#index: at: <%= absolute_time %>, tooltip <%= relative_time %>
Host#show: reported_at: <%= relative_time %>
Certs#index: cert: <%= relative_time %>, tooltip <%= absolute_time %>
... and so on

It's a slight increase in complexity over the initial proposal.
However, this way it'll still be much more consistent about how to
present information, and be easier to change formats in future, without
losing the option to display text in the way that makes the most sense
based on the context.

> Also I should have separated two things. At some pages (e.g. reports
> list) I'd like to change "ago" to timestamp. We can discuss every
> occurrence individually, when I send a PR, I'll post a link here.
> Based on above, I won't change e.g. smart proxy ca expiration.

+1 to gradual change, but let's define these helpers first, it'll make
the PRs for changes much smaller ;)

Greg

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

[foreman-dev] [Event] Foreman Community Demo Items - Thu 20 Apr 3pm [GMT]

[greg . sutcliffe]

Hi all

Demo time! As always, have a think for items which have been completed since
the last demo on 2017-03-30. There is a query that will show you items
completed (i.e. marked as closed) since the last demo [2].  Please add demo
items following the instructions on the agenda page [3].

If you can't be present but have something to show, add it to the agenda and
let me know - I'll be happy to talk about the feature in your absence. Please
do leave me enough time to familiarize myself with the content though :)

[1] https://www.youtube.com/watch?v=0sl4HgMzgio
[2] http://tinyurl.com/kmzwj3t
[3] 
http://projects.theforeman.org/projects/foreman/wiki/Current_Sprint_Information

Cheers!
--
Greg
IRC: gwmngilfen

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

[foreman-dev] [Event] Foreman Community Demo Items - Thu 13 Apr 3pm [GMT]

[greg . sutcliffe]

Hi all

Demo time! As always, have a think for items which have been completed since
the last demo on 2017-03-30. There is a query that will show you items
completed (i.e. marked as closed) since the last demo [2].  Please add demo
items following the instructions on the agenda page [3].

If you can't be present but have something to show, add it to the agenda and
let me know - I'll be happy to talk about the feature in your absence. Please
do leave me enough time to familiarize myself with the content though :)

[1] https://www.youtube.com/watch?v=0sl4HgMzgio
[2] http://tinyurl.com/kmzwj3t
[3] 
http://projects.theforeman.org/projects/foreman/wiki/Current_Sprint_Information

Cheers!
--
Greg
IRC: gwmngilfen

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

[foreman-dev] Foreman AMA - today, 3pm UK time

[Greg Sutcliffe]

Hi all,

Since all our developers are

*busy having cocktails^W^W^W
*sleeping off an Easter Chocolate coma^W^W^W^W^W
*really really busy with 1.15 testing :P

I've decided to change today's community demo to an Ask Me Anything.
I'll chair it, and I'll try to get some other notable people on the
show too.

Feel free to ask questions here in advance (or mail me direct if you
desire anonymity), or you can tune in live to ask during the show (on
IRC / YouTube chat)

https://www.youtube.com/watch?v=0sl4HgMzgio

See you at 3pm!
Greg
-- 
IRC / Twitter: @gwmngilfen
Diaspora: gwmngil...@joindiaspora.com

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

Re: [foreman-dev] Re: Revert removal of @host.params for host_param

[Greg Sutcliffe]

On Wed, 2017-04-19 at 14:10 +0300, Tomer Brisker wrote:
> Since it seems there wasn't an agreement on reverting this made in
> time for 1.15, I'd say we should support both for now and reconsider
> in the future pending a rewrite of the template engine using a proxy
> object as we discussed.

+1, supporting both seems like the way forward.

Greg

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

Re: [foreman-dev] Retire the RFC repo?

[Greg Sutcliffe]

I've been meaning to reply to this for about a week, sorry for the delay. This 
is a topic I've been thinking about for a *long* time, so apologies for the 
long thread :P

I think there's two issues here. One is *how* to have the discussion, and the 
other is how to *end* the discussion. From the comments so far, it seems we're 
still somewhat split on point 1, but we're all agreed we need to find a 
solution to point 2. As such, I'm only going to discuss point 2, as that's 
where we currently struggle.

For ways to end a discussion, I think there are several options. I've stayed 
away from this area for a while, because it can be fairly explosive, but it's 
clear we do need a way to conclude a discussion.

One choice is to have a group of people responsible for deciding on these 
things (a "technical council" or whatever title you wish to use). There's no 
doubt that this works, but I dislike this option but it's exclusive, requires 
a great deal of overhead (particularly documenting how the group works, and 
how to become a part of it, and so forth). As a data point, Libreoffice do 
this, with a similar order-of-magnitude of regular contributors.

Another is a simple vote, but then you have to balance the "when" and "how". 
Preserving the "quieter voices" (that is, people whose expertise is valuable, 
but who don;t want to wade into a big discussion) in our community is 
important, and votes are good for this, but close-to-50% votes can be very 
divisive. PHP use this method, with the extra clause that the author of the 
RFC gets to call the vote (after a minimum wait of 1 week from opening), and 
they find it works for them. 

We could also turn to 3rd party systems to help us with discussions - as an 
example, I believe the Diaspora development community use Loomio for their 
decision making, but I have no data on how well it's working for them. I#m not 
for this option - we already use enough tools - but others may like the idea.

At this time, my gut feeling is:

a) The group is split on the RFC repo, so let's not call it dead yet
b) The RFC repo works well(ish) as a place to discuss design
c) It needs process improvements to reflect how it's *actually* being used
d) We could add the vote system from PHP for closing discussions
e) (tangent) We could also use said vote system for foreman-dev discussions

As further info, here's the recording from my discussion at FOSDEM on this 
topic (where the above comments about Libreoffice and PHP come from, but 
there's a lot of interesting stuff in there):

http://mirror.onet.pl/pub/mirrors/video.fosdem.org/2017/UD2.119/
community_closing_loops.mp4

So, to the point - how would people feel about trialing this? We'd need to 
decide (a) if we want to test it, (b) how to call for & record votes, and (c) 
when to end the trial and decide on whether to keep it. If you're against this 
idea, please do suggest how else we might collectively improve our ways to 
finish discussions :)

Cheers
Greg

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

Re: [foreman-dev] CREATE host or hostgroup with new fields

[Greg Sutcliffe]

It's also worth noting that trying to assist with code problems is
almost impossible when we can't see the code. Do you have you plugin
available on the public internet somewhere (e.g. GitHub) for us to look
at?

Greg

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

Re: [foreman-dev] CREATE host or hostgroup with new fields

[Greg Sutcliffe]

On Wed, 2017-08-02 at 05:15 -0700, Fairouz el ouazi wrote:
> Hi Greg , 
>I did sent you a message i don't know if you get it ? 

You sent it to me personally instead of to the mailing list, and it got
filtered to a folder I don't often look at. Make sure you're replying
to the list rather than privately :)

You say you've not published the code - that makes it very difficult to
help you. It's almost impossible to say what the issue might be without
it - there are just too many unknowns.

Unless you have specific business reasons not to publish it, then I
would suggest grabbing a Git repo on GitHub or Gitlab, storing the code
then, and then replying with a link to where you're seeing issues in
your code. You've really nothing to lose, and everything to gain.

Cheers
Greg

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

Re: [foreman-dev] Aligning Foreman & Katello git repositories

[Greg Sutcliffe]

Overall, big +1 from me - it'll make my life easier too. Whilst I
appreciate Katello is a big project in it's own right, it's never felt
good to me that it lives in it's own world despite every other plugin
being in the Foreman namespace. Obviously there's historical reasons
for that, but tradition for tradtion's sake is no argument at all :)

Some thoughts on the various points:

# foreman-bats -> forklift merge

This does indeed feel like duplication of effort. It's also an area
where we have some flexibility, since we *can* choose to disable some
types of test in the short term if we need to (obviously thats not
ideal though). The path forward is clearly to get forklift where it
needs to be before removing bats for good, +1 there.

There's also the CentOS CI project, but I'll send a separate mail about
that since it's additional to bats/forklift rather than integral.

# katello-packaging -> foreman-packaging

Overall, in favour, it makes it possible for me to do better metrics on
Katello usage. 

About 1/3rd of our substantial budget from Rackspace goes on bandwidth,
but what I can't see is how much of that is our own consumption for
package building and testing. It may be worth looking into caching /
internal Rackspace-IP mirrors for our builders before we take the
plunge on this.

As for the modules / installer, +1 in general, no specific comments :)

If I can help at all from an infra perspective, let me know, especially
 if you need insights into the Rackspace usage etc.

Greg

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

[foreman-dev] Re: Taking over plugins - do we need a policy?

[Greg Sutcliffe]

https://github.com/theforeman/theforeman.org/pull/932

I'd like to look at a larger revamp of the plugins section of the site
in a while (there was another thread about this, I think) but this will
do for now.

I'll script up the list of plugins that need extra maintainers
tomorrow.

Greg

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

Re: [foreman-dev] Taking over plugins - do we need a policy?

[Greg Sutcliffe]

On Tue, 2017-08-15 at 08:20 +0200, Marek Hulán wrote:
> curl https://rubygems.org/api/v1/gems/foreman_chef/owners.json
> 
> see http://guides.rubygems.org/rubygems-org-api/#owner-methods for
> more details.

Ah, perfect, thanks. I'll get a policy drafted up and then I can script
this an mail all plugins that only have a single owner to ask them to
add another.

Greg

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

[foreman-dev] Re: Taking over plugins - do we need a policy?

[Greg Sutcliffe]

So, I should read our own docs

http://projects.theforeman.org/projects/foreman/wiki/How_to_Create_a_Pl
ugin#Making-your-plugin-official

I think this covers all we discussed, but perhaps it's on the owners
(myself, Eric, Ohad) to be more proactive about enforcing it when
migrating plugins to our Org on GitHub? I think is basically what
Dmitri is saying.

Also, given how buried this is, I'll make the PR about moving it to the
website... if/when it's merged we can update the wiki.

Greg

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

[foreman-dev] [Event] Foreman Community Demo Items - Thu 13 Jul 3pm [BST] - 8th Birthday Edition

[greg . sutcliffe]

Hi all

Demo time! This one happens to fall exactly on our birthday, so I'm looking
ideas to make it extra special. Ohad, would you like to be on this one? Anyone
else want to talk nostalgia for 20min? Any other ideas? :)

However, we do need some content too, so as always, have a think for items
which have been completed since the last demo on 2017-06-22. There is a
query that will show you items completed (i.e. marked as closed) since the last
demo [2].  Please add demo items following the instructions on the agenda page
[3].

If you can't be present but have something to show, add it to the agenda and
let me know - I'll be happy to talk about the feature in your absence. Please
do leave me enough time to familiarize myself with the content though :)

[1] https://www.youtube.com/watch?v=sL8KylTcqsg
[2] http://tinyurl.com/ydz7wyyn
[3] 
http://projects.theforeman.org/projects/foreman/wiki/Current_Sprint_Information

Cheers!
--
Greg
IRC: gwmngilfen

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

[foreman-dev] Taking over plugins - do we need a policy?

[Greg Sutcliffe]

Hi all,

I've been thinking for a while about plugins, and how to continue them
when original authors move on. It's only natural that developers will
come and go, so we need to think about how to deal with this. We've got
a few examples of this now, and have had others in the past.

1) I'm playing with Salt in my spare time at the moment, with a view to
(maybe) taking on the foreman_salt plugin, since Stephen is no longer
working on it. However, it's only chance that I know this fact -
there's no easy way for an author to mark a plugin as "orphaned".

2) Some plugins are awaiting changes but the author hasn't responded
(yet!). Foreman_bootdisk has some open PRs at the moment that fall into
this category (PRs 42, 43 for example), and default_hostgroup has pen
issues (oops!). Presumably we need a way to ping authors and find out
if they're just AFK or have stepped away from the plugin entirely.

3) Some plugins are definitely abandoned. I recall Chris Pisano taking
over the foreman_banner plugin last year and struggling to get in touch
with the original author at all.

For context, Fedora does have a policy for this that makes some sense:

https://fedoraproject.org/wiki/Policy_for_nonresponsive_package_maintai
ners

That's quite heavy, but some of the points make sense. So, do we need
to add something to our docs about this. My gut feeling is:

* Yes, we do
* Only applies to plugins in "theforeman" GitHub repo
* We need to add extra maintainers to the Rubygems *before* the author
leaves - Chris had a real issue here. This could be a requirement of
getting aplugin packaged, for example.
* We need to allow authors to "abandon" a plugin clearly (something
like how the Arch User Repository does it maybe?)

Thoughts?
Greg

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

Re: [foreman-dev] Katello with debian repositories

[Greg Sutcliffe]

This is awesome, thanks guys! Deb support for Katello has been on my
wishlist for a long time. In case you didn't see it, Leah Fisher was
working on something similar, albeit using the basic "file" type for
Pulp - a blog post was started at [1] but hasn't been finished yet. I
mention it mainly for context, since you've gone a different route :)

Looking forward to seeing the comments from the Katello devs. Assuming
all is well, we should do a deep dive into getting it set up and
working so that more people can test it for you.

[1] https://github.com/theforeman/theforeman.org/pull/872

Cheers
Greg

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

[foreman-dev] [Event] Foreman Community Demo Items - Thu 03 Aug 3pm [BST]

[greg . sutcliffe]

Hi all

Demo time! As always, have a think for items which have been completed since
the last demo on 2017-07-13. There is a query that will show you items
completed (i.e. marked as closed) since the last demo [2].  Please add demo
items following the instructions on the agenda page [3].

If you can't be present but have something to show, add it to the agenda and
let me know - I'll be happy to talk about the feature in your absence. Please
do leave me enough time to familiarize myself with the content though :)

[1] https://www.youtube.com/watch?v=rZY6dE0HVyM
[2] http://tinyurl.com/yaw2gyjf
[3] 
http://projects.theforeman.org/projects/foreman/wiki/Current_Sprint_Information

Cheers!
--
Greg
IRC: gwmngilfen

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

Re: [foreman-dev] Dropping Fedora 24 packages

[Greg Sutcliffe]

Forgot to add a link:

https://theforeman.org/2017/03/2017-foreman-survey-analysis.html#page1

Page down to the first table (not pie chart) in that section.

Greg

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

Re: [foreman-dev] foreman snapshot management

[Greg Sutcliffe]

On Wed, 2017-07-05 at 17:19 +0200, Matthias Dellweg wrote:
> Hi all,
> we wrote a plugin for Foreman, that allows to control the snapshot
> api of vSphere within the host view of foreman.
> You can take snapshots of running and stopped hosts, and you can
> rollback a host to such a snapshot.
> In the back, the plugin talks to the fog library.
> We tried to capsulate the snapshot logic in a way, that it shall be
> easy to implement support for other virtualization backends (compute
> resources).

Very cool! I had a similar plugin for Openstack and Libvirt a few years
back[1] which also went through Fog - maybe I should see if I can use
it to extend your plugin ;)

Greg

[1]https://github.com/GregSutcliffe/foreman_snapshot/

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

Re: [foreman-dev] [Infra] Service accounts and secret storage

[Greg Sutcliffe]

On Tue, 2017-06-27 at 13:03 +0200, Ewoud Kohl van Wijngaarden wrote:
> 
> What are the options to use a @theforeman.org email address? Looks
> like google now requires money for that where it used to be free.
> The advantage would be that we can easily change the provider
> without changing all accounts.

Ohad will have to answer this, he still manages the DNS - there may be
mailforward options there (I use mailforward records on my DNS, via
ZoneEdit / EasyDNS)

Greg

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

Re: [foreman-dev] [Infra] Service accounts and secret storage

[Greg Sutcliffe]

On Tue, 2017-06-27 at 17:43 +0300, Ohad Levy wrote:
> 
> Are you suggesting to host mail infra ourself

Nope.

> pay to google

Nope.

> or some other alternative? Changing DNS records is a non issue.

I'm talking about Mail Redirects or Mail Forwards - https://support.dns
imple.com/articles/email-forwarding/

In my DNS control panel at EasyDNS, there is a section marked "Mail
Forwards". These redirect incoming emails to other addresses, for
example:

scale...@theforeman.org -> greg.sutcli...@gmail.com

and so on. They are one way only (I can't send emails as the former,
only receive), but for site registrations / password recovery it's
ideal. In this case it would also be easy to update these targets if
the original person moves on.

I have no idea if your DNS has this feature though - in my case, I get
it for free on top of what I already pay for my DNS.

Greg

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

[foreman-dev] [event] Deep Dive: PXE booting in a pure IPv6 environment - Thurs 6th July, 2pm (UK)

[Greg Sutcliffe]

Hi all,

Dmitri Dolguikh (better known as 'witlessb' on IRC) has been deep in
the guts of IPv6 provisioning with Foreman for some time now, and he'd
like to share the results of his efforts. We'll be holding a deep dive
into this on Thrusday 6th July, at 2pm (GMT +1). You can tune in here:

https://www.youtube.com/watch?v=6KJne_Hyv5k

As ever, we'd love to have you with us live to put your questions to
Dmitri - you can use YouTube Live Chat, or hop into #theforeman on
Freenode IRC during the show.

Cheers,
Greg
-- 
IRC / Twitter: @gwmngilfen
Diaspora: gwmngil...@joindiaspora.com

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

[foreman-dev] [event] Deep Dive: Running the Foreman Stack in Containers - Mon 10th July, 2pm (UK)

[Greg Sutcliffe]

Hi all,

Running Foreman in a container is a question that comes up from time to
time in the Foreman community. Eric Helms has been experimenting with
running the whole Foreman stack (core, proxies, plugins) inside
Kubernetes, and wants to show you how it looks. We'll be holding a deep
dive into this on Monday 10th July, at 2pm (GMT +1). You can tune in
here:

https://www.youtube.com/watch?v=mPjUvNAYp1c

As always, we welcome your contributions to the video - do join us live
on YouTube Live chat or in our IRC channel to put your questions to
Eric!

Cheers,
Greg
-- 
IRC / Twitter: @gwmngilfen
Diaspora: gwmngil...@joindiaspora.com

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

[foreman-dev] Plugin gems with a single author

[Greg Sutcliffe]

Hi all,

As per the newly-merged plugin policy, I've taken a quick pass over all
the gems listed in the RPM packaging (which is more comprehensive than
the Deb packaging), grepped for "foreman" and "proxy", and then used
the Rubygems API to filter for gems with a single author.

This list was pretty long, so for brevity, I've also removed things
which are (as far as I know) not in active use at the moment (we can
always revisit that and run this again later).

Below is the list of gems that need an additional maintainer, grouped
by owner. Could these people please add a second author to the gem,
just in case? If you've got someone in mind just go for it, if you want
help deciding who show be added, feel free to reply here.

Daniel Lobato Garcia:
- foreman_ansible
- foreman_ansible_core
- foreman_azure
- foreman_cockpit

Dominic Cleal:
- foreman_bootdisk
- foreman_hooks
- foreman_setup
- hammer_cli_foreman_bootdisk
- smart_proxy_dns_route53

Ewoud Kohl van Wijngaarden:
- smart_proxy_dns_powerdns

Greg Sutcliffe:
- foreman_column_view
- foreman_default_hostgroup

Marek Hulan:
- foreman_chef
- smart_proxy_chef

Lukas Zapletal:
- smart_proxy_discovery_image

Ohad Levy:
- foreman_memcache

Since I'm on the list, who wants adding to my plugins? :)

Regards
Greg
-- 
IRC / Twitter: @gwmngilfen
Diaspora: gwmngil...@joindiaspora.com

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

[foreman-dev] Re: [Event] Foreman Community Demo Items - Thu 11 May 3pm [GMT]

[Greg Sutcliffe]

Friendly reminder that the demo is *tomorrow* and I still see very
little content on the agenda. Given we did an AMA last time, it's been
6 weeks since the last demo - is there really nothing to show since
then? Or is it a case of people not having enough time to spare?

Greg

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

[foreman-dev] [Deep Dive] Vertical Navigation Proposal, with Rox & Serena

[Greg Sutcliffe]

Hi all,

A while back there was a proposal for a vertical navigation for Foreman
[1,2]. This has been rumbling on for a while, so I felt it might be
time to shine a spotlight on it and get some fresh voices in the
discussion. When it comes to UI changes though, I find screenshots hard
to visualize, so perhaps a live demo is in order... :P

Accordingly, there will be a deep dive on Tuesday where Rox and Serena
will spend some time talking about what they feel is wrong with our
current UI (and horizontal UIs in general), how moving to a vertical
navigation helps, how it worked out for a couple of other communities,
and how it *might* look for us.

https://www.youtube.com/watch?v=hQwJ11GYfjY

To be clear, these are still *proposals* at this stage, and we
definitely want to hear from people about how they feel on this - what
you feel is wrong with the current UI, and how we might fix it. This is
one approach, but perhaps you have other suggestions :)

Feel free to join us live and ask questions to Rox & Serena via the
usual IRC or YouTube methods, or if you catch it later, we can continue
the discussion here on the mailing list.

Thanks!
Greg

1 https://groups.google.com/d/topic/foreman-dev/2dERjSniGzc/discussion
2 https://github.com/theforeman/foreman/pull/4302

-- 
IRC / Twitter: @gwmngilfen
Diaspora: gwmngil...@joindiaspora.com

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

Re: [foreman-dev] Nomination for an additional GitHub org owner

[Greg Sutcliffe]

On Mon, 2017-06-26 at 10:25 +0300, Tomer Brisker wrote:
> +1 to adding Eric, although that won't solve the issue of Ohad and
> Dominic being busy and having no owner available on this side of the
> globe.

That's fair, do you want to start a new nomination thread to address
that? :P

Greg

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

[foreman-dev] Nomination for an additional GitHub org owner

[Greg Sutcliffe]

Hi all,

Slightly different to our usual "nominate a new commiter" process, but
I'm wondering if we need to appoint a new owner on our GitHub
organisation?

Currently, only Dominic and Ohad are owners, and they are both
frequently busy with other things, which leads to some delays when
adding in new repos or moving things about. 2 people is also a fairly
high bus factor. I think it's time we added a third name to the owners
- we don't have an official process for this, but I'm treating like
commit access, so here's a nomination email.

Obviously, this is mainly a role for maintenance - creating/forking
repos, moving them, creating new teams, etc. rather than about merging
code. I think a we have a few people that would be a good fit - my
suggestion would be Eric Helms. He's experienced both in our structure
& in GitHub-y stuff, and is in a different timezone, which helps if
something comes up out of European hours.

Any comments/concerns/upvotes? :)

Cheers
Greg

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

Re: [foreman-dev] [Event] Foreman Community Demo Items - Thu 01 Jun 3pm [GMT]

[Greg Sutcliffe]

Hi Bernhard

On 26/05/17 21:32, Bernhard Suttner wrote:
> Hi,
> 
> Are you interested in having a demo about the foreman_scc_manager plugin
> which we have developed at ATIX?

I think that'd be great, you're definitely welcome to join the demo. We
generally stick to 10mins max for demo items - does that work for you?
If not we could do a Deep Dive instead (such as Timo & Dirk did recently
for their monitoring plugin).

Cheers
Greg

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

Re: [foreman-dev] Why does foreman support only one provisioning template per operating system?

[Greg Sutcliffe]

Hi there,

On Wed, 2017-05-24 at 09:02 -0700, nokrite wrote:
> Hello together,
> 
> i have a question about the architecture design of foreman, wich i
> dont understand from a users perspective.
> Why does foreman support only one provisioning user data template per
> operating system? I dont really understand the benefit from this,
> because i have some scenarios in my head, where it could be useful
> while provisioning a new host to chooese between different user data 
> templates. 

It is possible to have multiple templates for an OS. The choice on the
OS edit page simple sets the *default* one. However, it's not
immediately obvious, so you can be forgiven for missing it ;)

If you go to a particular template, and go to the Association tab,
after you've assigned the appropriate OSs to the template you'll see a
button marked "Valid host group and environment combinations". This
alows you to specify conditions for matching this template to a host,
based on Hostgroup and/or Environment.

Thus you could have:

* Preseed default - default in the OS page
* Preseed (Production) - matched if env == production
* Preseed (Webservers) - matched if production and in the Web group

and so on. This gives you flexibilty to choose templates based on the
needs of your individual hosts - just put them into a specific group or
env and click Resolve Templates to check it matched.

> I want to give two simple scenarios:
> 
> 1. I want to provisioning image based from a vmware template per
> foreman-vmware with a user data template. So maybe i want
> sometimes provisioning a host without static ip configuration and
> other times i want to provisioning with a static ip configuration. In
> this screnario i always have to edit the adapter settings in the user
> data template before i go to create a new host. Because if i have
> adapter settings in the user data template who expect ip adresses and
> so on, the provisioning process over vmware will fail if iam not
> providing this in foreman. If i want the host just get a random ip
> adress from the dhcp server and dont set it static, i have to kick
> the static adapter settings out of the user data template before
> creating a new host.

In addition to multiple templates, you can always use ERB to add
conditionals to templates, based on host parameters:

<% if @host.params['staic-ip'] == 'yup' %>
  do static stuff
<% end %>

Which allows your users to add little bits on an opt-in basis (I think
our default netowrking templates already have an option for static
IPs). You could also use configuration management to do most of the big
changes once the host is provisioned.

2. Another thing is, if i have multiple environments. I install over
> the user data template for example over powershell command the
> windows puppet agent. Also define there in wich environment i want
> to provisioning over installation arguments from the puppet agent msi
> file. So that meens that i always have to edit the user data template
> when i want to change the environment before creating a new host.
> Because in the new host dialouge i can choose the environment, but
> the agent dosent care and always use "production" if i didnt provide
> other environments over installation arguments.

Again, you want to use ERB to provide this kind of data, our default
templates do this for you (see https://github.com/theforeman/community-
templates/blob/develop/provisioning_templates/snippet/puppet.conf.erb#L
47 for how we set the environment).

> For me it would be the best if i just choose in the "new host"-
> dialogue image based provisioning"  and after i choose my operating
> system and click on "resolve" he return me a list of different user
> data templates for my needs and not only always one. So that every
> user can chooese what they need at that moment.

The main answer here is that the Host new/edit page is *waaay* too
complicated already, and adding more selectors won't help. It'd be
lovely to redesign it, if there was time :)

Greg

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

[foreman-dev] [Event] Foreman Community Demo Items - Thu 01 Jun 3pm [GMT]

[greg . sutcliffe]

Hi all

Demo time! As always, have a think for items which have been completed since
the last demo on 2017-05-11. There is a query that will show you items
completed (i.e. marked as closed) since the last demo [2].  Please add demo
items following the instructions on the agenda page [3].

If you can't be present but have something to show, add it to the agenda and
let me know - I'll be happy to talk about the feature in your absence. Please
do leave me enough time to familiarize myself with the content though :)

[1] https://www.youtube.com/watch?v=_OrYpestGQc
[2] http://tinyurl.com/lhwqdyh
[3] 
http://projects.theforeman.org/projects/foreman/wiki/Current_Sprint_Information

Cheers!
--
Greg
IRC: gwmngilfen

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

[foreman-dev] Re: [Event] Foreman Community Demo Items - Thu 01 Jun 3pm [GMT]

[Greg Sutcliffe]

Hi all,

Sadly I'm going to have to cancel today's demo - we have very few
presenters, so it would be very short anyway. Hopefully we'll have more
content for you next time!

Bernhard, I'll contact you separately about a Deep Dive for the SuSE
plugin. I think it warrants some attention :)

Greg

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

[foreman-dev] [Event] Foreman Community Demo Items - Thu 22 Jun 3pm [BST]

[greg . sutcliffe]

Hi all

Demo time! As always, have a think for items which have been completed since
the last demo on 2017-06-01. There is a query that will show you items
completed (i.e. marked as closed) since the last demo [2].  Please add demo
items following the instructions on the agenda page [3].

If you can't be present but have something to show, add it to the agenda and
let me know - I'll be happy to talk about the feature in your absence. Please
do leave me enough time to familiarize myself with the content though :)

[1] https://www.youtube.com/watch?v=uUFsHWF292M
[2] http://tinyurl.com/yc57afvf
[3] 
http://projects.theforeman.org/projects/foreman/wiki/Current_Sprint_Information

Cheers!
--
Greg
IRC: gwmngilfen

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

[foreman-dev] [Event] Foreman Community Demo Items - Thu 11 May 3pm [GMT]

[greg . sutcliffe]

Hi all

Demo time! As always, have a think for items which have been completed since
the last demo on 2017-04-20. There is a query that will show you items
completed (i.e. marked as closed) since the last demo [2].  Please add demo
items following the instructions on the agenda page [3].

I'd like to cover some of Summit, but since I wasn't there, I'll need help with
that. Volunteers? :)

If you can't be present but have something to show, add it to the agenda and
let me know - I'll be happy to talk about the feature in your absence. Please
do leave me enough time to familiarize myself with the content though :)

[1] https://www.youtube.com/watch?v=Yj4LytgUUc4
[2] http://tinyurl.com/ku7xjjw
[3] 
http://projects.theforeman.org/projects/foreman/wiki/Current_Sprint_Information

Cheers!
--
Greg
IRC: gwmngilfen

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

Re: [foreman-dev] [RFC] - Proxies with multiple interfaces

[Greg Sutcliffe]

On 04/05/17 17:22, Sean O'Keeffe wrote:

> *I think I'll redo this as the following unless anyone has any
> objections..* I know we don't really want to include another join but i
> don't see any other way to cater for LoadBalanced & Multi-homed Smart
> Proxies.
> 
> - A new SmartProxyHostname model (with name & hostname attrs) with a
> has_and_belongs_to_many relationship to SmartProxy and vise versa.
> - A new Smart Proxy Hostnames entry under the "Infrastructure" menu item.
> - On Smart Proxy creation a Hostname would also be created from the URL
> with the same Name as the Smart Proxy (so complexity isn't increased for
> simple deployments)
> - Hosts & Hostgroups objects would select a Hostname by Name. (this
> would be transparent as by default the Hostname would have the same name
> as the Smart Proxy)

Given that Hosts can already be multihomed, and have a name per nic,
does itmake sense to store this in the Interfaces table, instead of
creating a new table? If the code is sufficiently different, the
Interfaces model is STId too, so you *could* create an Interface::Proxy
model if need be.

I *think* that would get you want you need, no? UI side sounds sane
enough, as do the defaults, it'd just mean re-using the code we already
have for things with multiple names.

Greg

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

Re: [foreman-dev] [Infra] Service accounts and secret storage

[Greg Sutcliffe]

On Tue, 2017-06-27 at 11:37 +0200, Michael Moll wrote:
> Hi,
> 
> While I don't like GMail, that sounds like a sensible way to go,
> lacking the alternatives.

I agree, but it's just for password recovery and so forth, so that it's
not tied to a single person. I don't expect to use it for anything
else.

> In addition to pass, Ewoud already mentioned, I was recommended
> passbolt (https://www.passbolt.com) and gopass (https://www.justwatch
> .com/gopass), which is a rewrite of pass.

I'll check those out, but tbh I'm wary of adding yet more 3rd-party
SaaS systems (even if they're FOSS), it's just more dependencies.
Thinking about it, a GPG encypted file somwehere on
downloads.theforeman.org would be enough, no?

On Tue, 2017-06-27 at 06:20 -0400, Eric D Helms wrote:
> Throwing yet another idea out there. Ansible Vault allows encrypting
> yaml key value files and storing the encrypted file in git so that it
> can be shared and stored in source control.

Maybe I'm missing something, but where's the value in Ansible here?
We're not talking about API secrets for automation, we're talking about
login details for the various services we use - i.e. for use by humans.

Greg

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

Re: [foreman-dev] [Infra] Service accounts and secret storage

[Greg Sutcliffe]

On Tue, 2017-06-27 at 11:37 +0200, Michael Moll wrote:
> 
> In addition to pass, Ewoud already mentioned, I was recommended
> passbolt (https://www.passbolt.com) and gopass (https://www.justwatch
> .com/gopass), which is a rewrite of pass.

Ugh, do research before writing :P

So pass / gopass not hosted, just passblot - possible, but would
require us to either host a simple git repo on the foreman infra (not a
big deal if it's SSH-access only anyway), or store it on GitHub
(probably not a good idea). Happy to go down that road if thats the
consensus.

Greg


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

Re: [foreman-dev] Bootdisk members (was Plugin gems with a single author)

[Greg Sutcliffe]

On Mon, 2017-09-11 at 13:02 +0100, Greg Sutcliffe wrote:
> 
> With no response here, or on various pull requests [1,2] in some
> months, would anyone object if I add Lukas and Timo to the bootdisk
> plugin on GitHub? They could then review each others work as we
> normally do.

On Tue, 2017-09-12 at 17:50 +0200, Marek Hulán wrote:
> Makes sense to me

I see a +1 from Marek and no -1's, public or privately, so this is now
done. Thanks all.

Greg

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

Re: [foreman-dev] Building an Infra/Deployment/Platform Roadmap

[Greg Sutcliffe]

So, +1 to this idea, we've been lacking in direction for a bit, and a
"community roadmap" has been on my agenda for a while. Whilst that's
not 1:1 the same as what you're saying, it's related, and planning is a
good idea.

On Mon, 2017-09-18 at 11:21 -0400, Eric D Helms wrote:
> 
> [1] http://pad-katello.rhcloud.com/p/infra-deployment-roadmap

Two things - firstly, isn't this hosted on Openshift v2, which is going
away soon? Secondly, are you aware of http://projects.theforeman.org/pr
ojects/foreman/wiki/Infrastructure_Updates on the wiki?

Combining those two points, would it be better to have this in the wiki
rather than on an etherpad?

>From my side, I'm working with Michael on upgrading the Puppet/Foreman
infra, and with Evgeni on migrating/upgrading Redmine. I don't think
either of these is controversial, but it's out there for the record ;)

Greg

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

[foreman-dev] Community-developed Ansible modules for Foreman API objects

[Greg Sutcliffe]

Hi all,

We're seeing more and more interest in Ansible within the Foreman
community, and one facet of that is the ability to deploy Foreman
itself using Ansible. That obviously requires a set of resources that
use the Foreman API to create/update objects in Foreman. That effort
has already been started with the ansible-modules repo [1] which uses
Nailgun [2] underneath. At present, there are 5 Foreman resources in
this repo (and another 12 Katello ones).

However, there is also a community member workingon this in parallel
[3] using a different Python layer [4] underneath. That repo contains a
much larger / more complete set of API resources, and it would be a
shame not to use it, and to give credit to it's creator.

So, this is a call for collaboration on how to bring these together.
I've reached out to Nosmoht (BCC'd on this mail, hi!) and he's willing 
to participate in this effort, so next we'll be needing a few more
volunteers to join in, and discuss how to proceed. From my perspective,
I think it makes sense to continue to use the "theforeman" repo for now
(things under our namespace are easier to promote as 'official'), merge
in Nosmoht's modules (and make him a committer / maintainer) and then
work on standardising all the modules to use the same underlying tool
(and deate which one it should be). Once we're happy with the stability
of the repo, we can consider trying to get it added to the Ansible
repos.

Thoughts?

Cheers
Greg

[1] https://github.com/theforeman/foreman-ansible-modules
[2] https://github.com/SatelliteQE/nailgun
[3] https://github.com/Nosmoht/ansible-module-foreman
[4] https://github.com/Nosmoht/python-foreman

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

Re: [foreman-dev] Requesting discovery test for core PRs

[Greg Sutcliffe]

On Thu, 2017-09-28 at 16:51 +0200, Evgeni Golov wrote:
> On Wed, Sep 27, 2017 at 7:26 PM, Timo Goebel 
> wrote:
> > ... have you considered using some kind of a CDN for downloads,
> > e.g. cloudflare, if traffic is a concern?
> 
> fastly.com is usually happy to sponsor bandwidth for FOSS projects,
> if you ask nicely (they sponsor one half of deb.debian.org, for
> example, the other half is sponsored by AMZN).
> 
> I could talk to the relevant people if that is something we want.

THis has gone rather quiet here, but I've not heard any opposition to
trying a CDN for the package downloads. Assuming no one has an
objection, we can start looking at this shortly.

Greg

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

Re: [foreman-dev] Access to foreman-infra

[Greg Sutcliffe]

On Mon, 2017-09-25 at 14:01 +0200, Ewoud Kohl van Wijngaarden wrote:
> Hello all,
> 
> To get more involved in foreman infra I'd like to request push access
> to foreman-infra. At first I'd like to help more with the CI.

That's over a week, no concerns - welcome to the infra team Ewoud :)

Greg

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

[foreman-dev] Redmine running slowly

[Greg Sutcliffe]

Since the start of this week Redmine has been consistently slow.
Console shows very high load (not dropping below 10, often above 20).
We haven't chnaged anyhting, so my suspicions are on the v2 sunset that
happened at the end of last week.

I've opened a support case to see what's going on, but for now treat
Redmine with care ;)

Greg

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

Re: [foreman-dev] Redmine running slowly

[Greg Sutcliffe]

On Tue, 2017-10-10 at 10:50 -0400, Andrew Kofink wrote:
> Me as well. It's quite difficult to work this way.

Yeah, I know :(

Openshift aren't saying much other than that this is mainly due to the
number of people that decided to upgrade to Silver Tier to avoid the
sunset of v2. That's putting a lot of load on the v2 cluster, which
obviously is hitting us. 

As Ewoud said, we've made a change today in how we process the
underlying cron jobs that should reduce the amount of IO we were doing
- if there's any kind of quota-ing going on, that should help. We're
seeing that bring the time taken to run the cron down to about 10mins
(starting at the top of the hour). That should improve things during
that period. Sadly I did make a mistake during a manual part of the
changes that impacted the DB, but that should be resolved now.

Base load now seems to be down to around 7-9 which is better but still
too high. Sadly the v3 resources are unlikely to be available before
November, which is a limiter. If things are not better in the next day
or two, then on Thu or Fri I may migrate it to our Scaleway account
anyway, as we have capacity there, although I'd rather not migrate
twice...

Greg

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

Re: [foreman-dev] Availablity of yum.theforeman.org

[Greg Sutcliffe]

On Fri, 2017-10-13 at 15:01 +0200, Ewoud Kohl van Wijngaarden wrote:
> 
> I don't see why we would have timeout but I can't investigate that 
> because I don't have access to any monitoring.

There's isn't any really (we should add that to the Infra TODO list).
`dmesg` doesn't show any of the conntrack issues we had a few weeks
back.

The httpd error logs are ofc full of the errors caused by the welcome
page. Now it's gone I'll monitor it and we'll see if anything else
comes up - Dirk, do you have an example of the issue you're seeing?

Greg

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

Re: [foreman-dev] foreman_tasks V1 endpoint works but V2 returns 404

[Greg Sutcliffe]

On Mon, 2017-10-16 at 22:15 -0700, rajesh.eras...@gmail.com wrote:
> # curl --user sledge:hammer -H "Content-Type:application/json" -k htt
> ps://ind2q00katello01.qa.local/foreman_tasks/api/V2/tasks/3574500b-
> 0394-4a94-9f86-8ff1890ceadb

I think this is a character-case issue - it's *v2* not *V2*. I can
replicate the 404 using V2.

Greg

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

[foreman-dev] FOSDEM / CfgMgmtCamp 2018 - Call for Presentations!

[Greg Sutcliffe]

Hi all,

It's that time of year again - the call for presentations for our
yearly conference season is now open!

FOSDEM - https://penta.fosdem.org/submission/FOSDEM18
CfgmgmtCamp - http://cfgmgmtcamp.eu/#cfp

This year is the 5th CfgMgmtCamp, and we want to make it the best yet.
So in addition to the usual developer updates, new plugins, and
community news talks, I'm very keen to hear from *users* - that's you!

Submit your success stories (or horror stories!), things you learned in
the trenches, or interesting ways you've put Foreman to use, and we'll
make sure that the users get a voice in this years Foreman track.

See you there!
Greg

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

Re: [foreman-dev] Redmine running slowly

[Greg Sutcliffe]

Things are no better today, and I'm out of patience with Openshift.
I've spun up an instance on Scaleway that should be able to cope and am
in the process of creating a copy of Redmine there. Once it's ready
I'll stop Openshift, re-import the db and cut over the DNS.

Continue to use Redmine as normal for now, I'll update when we're ready
to do the final cutover.

Greg

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

Re: [foreman-dev] Redmine running slowly

[Greg Sutcliffe]

On Wed, 2017-10-11 at 21:52 +0300, Ohad Levy wrote:
> 
> > redmine01.theforeman.org A 51.15.192.166
> > redmine01.theforeman.org  2001:bc8:4400:2300::5:e03
> 
> both should be resolved.

Thanks Ohad.

SMTP is now unblocked and confirmed working, so we're ready to switch
over. As soon as I can get a timeframe from Ohad for when the DNS
change can be done, I'll arrange a maintenance window.

Hang in there guys, we're almost done ;)

Greg

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

Re: [foreman-dev] Redmine running slowly

[Greg Sutcliffe]

We're ready to switch. I'll take Redmine offline in about 30mins (11.15
UK time) and we should be back up on the new host at 12 noon. Please
save your work ;)

Greg

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

Re: [foreman-dev] Redmine running slowly

[Greg Sutcliffe]

And we're back. Please test extensively and report issues ;)

In particular, we're now on Ruby 2.0 (up from 1.9 on Openshift) so I
suspect the plugins might have issues. Any issues, please report them
here and we'll take a look. I checked quickly and didn't see any
errors, but I was in a hurry :P

Things still to do:

* Add logrotate for the production.log files
* Add HTTPS (ewoud is on that)
* Upgrade to latest Redmine (I'm looking into it)
* Puppetize it so we can migrate more easily in future

We'll monitor to see if the resources are enough, let me know if you
see any issues (no, Backlogs does not count, that thing is *slow* :P)

Thanks for your patience everyone.
Greg

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