Re: [foreman-dev] Jenkins can now send email

[Greg Sutcliffe]

On Thu, 2017-10-26 at 15:53 +0200, Lukas Zapletal wrote:
> Ok added me into the list in the post-build action.

Cool, trigger a build and see if you get an email :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.


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

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

[Eric D Helms]

On Tue, Oct 24, 2017 at 3:47 PM, Thomas Krahn 
wrote:

> Hi all,
>
> as the maintainer of the Ansible Foreman modules
>  i would like to share
> my thoughts with you.
>
> First of all i really like the idea to bring Foreman modules into Ansible.
> The complete configuration of Foreman is much easier if you can use
> Infrastructure as Code.
> That was the reason why i started the implementation in March 2015. At
> this time Ansible didn't have the module_utils folder and modules had to be
> "self contained".
> So the only way to use shared code was to create a Python library and use
> it. My result of that constraint is the Python Foreman library
> .
> It was and still is a challenge to always sync the modules and the library
> functionality.
>
> As far as i can see Nailgun is the library to work with Satellite 6 API.
>
> In regards to the future used library i see three different options so far:
> 1. nailgun
> 2. python-foreman
> 3. Ansible's module_utils.
>
> I don't want to talk about functionality here, but more about constraints
> and dependencies.
> If either nailgun or python-foreman is used people would have to install
> the library to use the Ansible modules and could have the same sync issue
> like i had in the past.
> Besides that i believe the library would have even more dependencies
> (python-requests for example) which could make things even more worst.
> On the other hand people would have a Python library that could even be
> used outside of Ansible for other tasks.
>

> If all that stuff is put into Ansible's module_utils folder we wouldn't
> have any sync issue nor external dependencies, but the usage would be
> limited to Ansible.
> And Ansible provides a great framework that abstracts a lot of things
> (methods like fetch_url() and open_url()) that otherwise would have to be
> reimplemented.
>
> Long term speaking i believe a common Python library would be the winner
> as it provides a standardized and well tested Foreman/Satellite interface
> to the world.
>
> I'm not sure how far the nailgun development is, but python-foreman is
> open source and i'm happy to hand out the ownership of that repository.
>

The idea of entirely self contained Ansible modules is a nice one,
especially from a user perspective at first. I say at first, because once
things are setup the user has less to worry about. And, at least currently,
I think there is some precedence among modules in Ansible today requiring
outside python packages. If no python API was being used today to talk to
Foreman I'd jump right on this option.

Given that there are at least two python API projects, one of which, as
Andrew points out, is actively used and contributed to by a large QE team
leads me to conclude external API package should win out to reduce
repeating ourselves, fixing the same issues in multiple places and
diverging. Sometimes, when the goals differ enough, creating a separate way
to do similar things can be beneficial, in this case I don't think they
differ enough.

We are in discussion with the team that owns Nailgun to bring it into the
community proper. One benefit to it is that it has Foreman plugin support
built into it already (e.g. Katello). There is a likelihood of a gap
existing between the two API projects that we'd need to resolve.

I will say, I can be swayed if shown that writing and supporting the API is
not that difficult, but I do tend towards community effort in one place if
we can.


>
>
>
> Next topic: Ansible modules
>
> I've already done a lot of work to move the modules from python-foreman +
> modules into "everything in Ansible".
> Means all the library stuff goes into module_utils/foreman.py plus all the
> modules in modules/cloud/foreman/*.py.
> Nearly 75% of that work is done so i could open a PR for each module that
> is already finished.
> If that's something the community would like to see...let's do it :-)
>

I assume here you are talking about moving modules into ansible/ansible for
delivery via 'package-management-tool install ansible' and making them
available system wide? If so, some info and thoughts. Currently there is
some raw building blocks there now from a time when I tried to be too smart
with some modules I had made:

https://github.com/ansible/ansible/tree/devel/lib/ansible/modules/remote_management

This is not in cloud as you suggested, as I thought cloud would pigeonhole
Foreman and plugins too much given it does so much more than simply cloud.
Given manageiq modules are in this same directory, I tend towards feeling
this is the right spot for management projects like ours.

The second point I think worth discussing is at what level and time should
we push modules to ansible/ansible versus providing them via a stand alone
git repository. I think there are pros and cons to both when it comes to
managing the modules, getting changes into the modules, developing new
modules or fu

Re: [foreman-dev] Heads up - hound rubocop version updated

[Lukas Zapletal]

Thanks Tomer!

LZ

On Thu, Oct 26, 2017 at 4:13 PM, John Mitsch  wrote:
> This was fixed on katello by https://github.com/Katello/katello/pull/7036
>
> If you have an open PR on katello, you may want to re-kick off Jenkins
>
> -John
>
> John Mitsch
> Red Hat Engineering
> (860)-967-7285
> irc: jomitsch
>
> On Wed, Oct 25, 2017 at 1:18 PM, Andrew Kofink  wrote:
>>
>> I created an issue in Katello [1] to track the changes there. We may
>> assign someone [who isn't there] during today's triage.
>>
>> [1] http://projects.theforeman.org/issues/21468
>>
>> On Wed, Oct 25, 2017 at 7:32 AM, Tomer Brisker 
>> wrote:
>>>
>>> Hi,
>>>
>>> Hound have updated their version of rubocop to 0.51 which includes some
>>> rule name changes. I have opened a PR [1] to foreman-core to upgrade to the
>>> latest version and updated the todo file.
>>> All plugins using rubocop should make sure their .rubocop.yaml is
>>> compatible with the new version.
>>>
>>> Hound ignores the rubocop version specified in the gemfile, which means
>>> that it will start barking on every PR in repos that use it if the settings
>>> are incompatible, and once the PR is merged into foreman core, those plugins
>>> depending on core and running rubocop on jenkins will start failing.
>>>
>>> The changes to rubocop's rule names can be foun in their changelog [2],
>>> or by manually running rubocop version 0.51 with your current configuration
>>> and looking out for errors. In case the errors are in the .rubocop_todo.yaml
>>> file, it can be automatically regenerated by running `rubucop
>>> --auto-gen-config` (but keep in mind this will disable any currently failing
>>> cops).
>>>
>>>
>>> [1] https://github.com/theforeman/foreman/pull/4949
>>> [2] https://github.com/bbatsov/rubocop/blob/master/CHANGELOG.md
>>>
>>> --
>>> Have a nice day,
>>> Tomer Brisker
>>> Red Hat Engineering
>>>
>>> --
>>> 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.
>>
>>
>>
>>
>> --
>> Andrew Kofink
>> akof...@redhat.com
>> IRC: akofink
>> Software Engineer
>> Red Hat Satellite
>>
>> --
>> 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.
>
>
> --
> 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.



-- 
Later,
  Lukas @lzap Zapletal

-- 
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] Centralizing tool_belt in theforeman Github

[Eric D Helms]

I've began this process by capturing what I believe is everything from [1]
as an PR to the mainline tool_belt repository:

https://github.com/ehelms/tool_belt/pull/58

Once this is approved, I will do the delete and transfer dance.


[1] https://github.com/theforeman/tool_belt

On Mon, Oct 23, 2017 at 9:08 AM, Andrew Kofink  wrote:

> +1 I guess the foreman and katello config files will still live separately
> (i.e. katello_35.yaml and foreman_16.yaml) but in the same repo.
>
> On Mon, Oct 23, 2017 at 5:59 AM, Daniel Lobato Garcia  > wrote:
>
>> On 10/20, Eric D Helms wrote:
>> > For quite a few releases now, we've been using a little tool named
>> > tool_belt as a CLI to perform release tasks such as finding cherry
>> picks,
>> > or building koji configurations. The larger idea of the repository is
>> you
>> > define a release via a configuration file and perform various release
>> > actions based on the data within the config file. The original
>> repository
>> > lives on my personal Github account [1]. At some point, this was forked
>> to
>> > theforeman organization and configurations for just Foreman stored in
>> it.
>> > Meanwhile, in the original repository are configs for Katello releases.
>> >
>> > I would like to propose merging the configuration files from theforeman
>> to
>> > my original repository, deleting thetheforeman fork and then
>> transferring
>> > my repository to theforeman to serve as the single shared repository. If
>> > you have any concerns, objections or questions please raise them here.
>> >
>> > If there are no objections, I will perform this next Wednesday or
>> Thursday.
>> >
>> >
>> > [1] https://github.com/ehelms/tool_belt
>> > [2] https://github.com/theforeman/tool_belt
>> >
>> > --
>> > Eric D. Helms
>> > Red Hat Engineering
>> >
>> > --
>> > 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.
>>
>> +1, I would also like to merge https://github.com/dlobatog/fo
>> reman_release
>> into that repository, making each of the scripts a subcommand of tool_belt
>>
>> --
>> Daniel Lobato Garcia
>>
>> @dLobatog
>> blog.daniellobato.me
>> daniellobato.me
>>
>> GPG: http://keys.gnupg.net/pks/lookup?op=get&search=0x7A92D6DD38D6DE30
>> Keybase: https://keybase.io/elobato
>>
>> --
>> 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.
>>
>
>
>
> --
> Andrew Kofink
> akof...@redhat.com
> IRC: akofink
> Software Engineer
> Red Hat Satellite
>
> --
> 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.
>



-- 
Eric D. Helms
Red Hat Engineering

-- 
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] Heads up - hound rubocop version updated

[John Mitsch]

This was fixed on katello by https://github.com/Katello/katello/pull/7036

If you have an open PR on katello, you may want to re-kick off Jenkins

-John

John Mitsch
Red Hat Engineering
(860)-967-7285
irc: jomitsch

On Wed, Oct 25, 2017 at 1:18 PM, Andrew Kofink  wrote:

> I created an issue in Katello [1] to track the changes there. We may
> assign someone [who isn't there] during today's triage.
>
> [1] http://projects.theforeman.org/issues/21468
>
> On Wed, Oct 25, 2017 at 7:32 AM, Tomer Brisker 
> wrote:
>
>> Hi,
>>
>> Hound have updated their version of rubocop to 0.51 which includes some
>> rule name changes. I have opened a PR [1] to foreman-core to upgrade to the
>> latest version and updated the todo file.
>> All plugins using rubocop should make sure their .rubocop.yaml is
>> compatible with the new version.
>>
>> Hound ignores the rubocop version specified in the gemfile, which means
>> that it will start barking on every PR in repos that use it if the settings
>> are incompatible, and once the PR is merged into foreman core, those
>> plugins depending on core and running rubocop on jenkins will start failing.
>>
>> ​The changes to rubocop's rule names can be foun in their changelog [2],
>> or by manually running rubocop version 0.51 with your current configuration
>> and looking out for errors.​ In case the errors are in the
>> .rubocop_todo.yaml file, it can be automatically regenerated by running
>> `rubucop --auto-gen-config` (but keep in mind this will disable any
>> currently failing cops).​
>>
>>
>> ​[1] https://github.com/theforeman/foreman/pull/4949
>> [2] ​https://github.com/bbatsov/rubocop/blob/master/CHANGELOG.md
>>
>> --
>> Have a nice day,
>> Tomer Brisker
>> Red Hat Engineering
>>
>> --
>> 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.
>>
>
>
>
> --
> Andrew Kofink
> akof...@redhat.com
> IRC: akofink
> Software Engineer
> Red Hat Satellite
>
> --
> 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.
>

-- 
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] Merge rights to Katello installer

[Lukas Zapletal]

+1 nice work thanks.

LZ

On Thu, Oct 26, 2017 at 11:39 AM, Sean O'Keeffe  wrote:
> Hi,
>
> I'd like to request write access to the installer team.
>
> I've been involved with 38 PRs across what I'd consider to be the 'main'
> repos, apparently I created 15 of them and I guess I reviewed the rest.
>
> https://github.com/Katello/puppet-katello/pulls?q=is%3Apr%20involves%3Asean797%20
> https://github.com/Katello/katello-installer/pulls?utf8=%E2%9C%93&q=is%3Apr%20involves%3Asean797
> https://github.com/Katello/puppet-certs/pulls?utf8=%E2%9C%93&q=is%3Apr%20involves%3Asean797%20
> https://github.com/Katello/puppet-candlepin/pulls?utf8=%E2%9C%93&q=is%3Apr%20involves%3Asean797%20
> https://github.com/Katello/puppet-foreman_proxy_content/pulls?utf8=%E2%9C%93&q=is%3Apr%20involves%3Asean797
> https://github.com/Katello/puppet-pulp/pulls?utf8=%E2%9C%93&q=is%3Apr%20involves%3Asean797%20
> https://github.com/Katello/puppet-qpid/pulls?utf8=%E2%9C%93&q=is%3Apr%20involves%3Asean797
>
> Thanks,
> Sean
>
> --
> 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.



-- 
Later,
  Lukas @lzap Zapletal

-- 
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] Jenkins can now send email

[Lukas Zapletal]

Ok added me into the list in the post-build action.

LZ

On Thu, Oct 26, 2017 at 2:58 PM, Greg Sutcliffe  wrote:
> On Thu, 2017-10-26 at 14:50 +0200, Lukas Zapletal wrote:
>> Greg, thanks for doing this. Now, honestly I do not understand a
>> single paragraph here.
>>
>> Can you show me an example JJB patch how to enable this for a plugin?
>> Ideally discovery, with my spam eating lzap+...@redhat.com :-)
>
> I haven't looked at what's needed in JJB yet, so this is all temporary
> at the moment. I made the needed change on the discovery job[1] (that
> is, add post-build action with no triggers), so if you go there now,
> you should see a Watch Job link. Try it out, let me know if it works.
>
> [1] http://ci.theforeman.org/job/test_plugin_foreman_discovery_develop/
>
> 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.



-- 
Later,
  Lukas @lzap Zapletal

-- 
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] Koji Outage

[Lukas Zapletal]

Here is an update. Restart did not help, we stopped the instance and I
am following this guide to create new AMI and start it:

http://docs.aws.amazon.com/AWSEC2/latest/UserGuide/creating-an-ami-ebs.html

Image which is now pending completion is called ami-2ecd6b54 and it
has both root EBS volume and data EBS volume (900 GB) which is the
reason why this is so slow. Then we can start new AMI to see if it
boots up. The instance type was i3.xlarge for the record, we want the
same one which was the best performance/price ratio for Koji workload.

After new koji boots up we want to recreate /mnt/tmp folder structure
and swap. Open /mnt/fstab to see the mountpoints, the i3.xlarge has
like 950 GB ephemeral storage, but it was unused (we had 400 GB swap
and 400 GB /mnt/tmp). In the /mnt/tmp directory there was just few
directories where koji was doing building locally. More CPU intensive
flavours were more expensive so we had this IO intensive one instead
which stills delivers 4 cores and 32 GB RAM which is good.

On the main EBS volume (900 GB one) there is a backup directory and in
this directory we should have a backup of the directory structure.
There is a cron job that does this daily. It was not backing up
temporary files, just directories. This should be enough to get koji
daemons back online. There should be a daily backup of postgre
database as well.

The EBS volume snapshot is ongoing, it is required to do snapshot
first and then you can create new AMI from it. I have some family
business in an hour, so I am writing this summary so someone else form
US timezone can carry on from here. Next step would be - start new
instance, let it boot (there might be ext4 file system check - not
sure if we use XFS or ext4 for the data volume - see the AMI console
for boot) and then find the /mnt/tmp backups, restore the directory
structure, restart (rather whole system than just koji) and it should
show up. Last thing would be to associate the elastic IP.



On Thu, Oct 26, 2017 at 2:56 PM, Lukas Zapletal  wrote:
> Likely a hardware failure according to notification, our instance is
> not responding. We are trying restart first.
>
> ***
>
> EC2 has detected degradation of the underlying hardware hosting your
> Amazon EC2 instance associated with this event in the us-east-1
> region. Due to this degradation, your instance could already be
> unreachable. After 2017-10-30 00:00 UTC your instance, which has an
> EBS volume as the root device, will be stopped.
>
> You can see more information on your instances that are scheduled for
> retirement in the AWS Management Console
> (https://console.aws.amazon.com/ec2/v2/home?region=us-east-1#Events)
>
> * How does this affect you?
> Your instance's root device is an EBS volume and the instance will be
> stopped after the specified retirement date. You can start it again at
> any time. Note that if you have EC2 instance store volumes attached to
> the instance, any data on these volumes will be lost when the instance
> is stopped or terminated as these volumes are physically attached to
> the host computer
>
> * What do you need to do?
> You may still be able to access the instance. We recommend that you
> replace the instance by creating an AMI of your instance and launch a
> new instance from the AMI. For more information please see Amazon
> Machine Images (http://docs.aws.amazon.com/AWSEC2/latest/UserGuide/AMIs.html)
> in the EC2 User Guide. In case of difficulties stopping your
> EBS-backed instance, please see the Instance FAQ
> (http://aws.amazon.com/instance-help/#ebs-stuck-stopping).
>
> * Why retirement?
> AWS may schedule instances for retirement in cases where there is an
> unrecoverable issue with the underlying hardware. For more information
> about scheduled retirement events please see the EC2 user guide
> (http://docs.aws.amazon.com/AWSEC2/latest/UserGuide/instance-retirement.html).
> To avoid single points of failure within critical applications, please
> refer to our architecture center for more information on implementing
> fault-tolerant architectures: http://aws.amazon.com/architecture
>
> LZ
>
> On Thu, Oct 26, 2017 at 1:51 PM, Eric D Helms  wrote:
>> Our Koji is currently down from a web perspective and ssh access. Please
>> don't merge anything further to -packaging until we've resolved this. All
>> actions requiring Koji repositories for testing or actions in Koji cannot be
>> performed.
>>
>> If Bryan or Lukas (since I am not sure who has AWS access to the box) could
>> investigate for us please.
>>
>> --
>> Eric D. Helms
>> Red Hat Engineering
>>
>> --
>> 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.
>
>
>
> --
> Later,
>   Lukas @lzap Zapletal



-- 
Later,
  Lukas @lzap Zapletal

-- 
You received this message 

Re: [foreman-dev] Jenkins can now send email

[Greg Sutcliffe]

On Thu, 2017-10-26 at 14:50 +0200, Lukas Zapletal wrote:
> Greg, thanks for doing this. Now, honestly I do not understand a
> single paragraph here.
> 
> Can you show me an example JJB patch how to enable this for a plugin?
> Ideally discovery, with my spam eating lzap+...@redhat.com :-)

I haven't looked at what's needed in JJB yet, so this is all temporary
at the moment. I made the needed change on the discovery job[1] (that
is, add post-build action with no triggers), so if you go there now,
you should see a Watch Job link. Try it out, let me know if it works.

[1] http://ci.theforeman.org/job/test_plugin_foreman_discovery_develop/

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

Re: [foreman-dev] Koji Outage

[Lukas Zapletal]

Likely a hardware failure according to notification, our instance is
not responding. We are trying restart first.

***

EC2 has detected degradation of the underlying hardware hosting your
Amazon EC2 instance associated with this event in the us-east-1
region. Due to this degradation, your instance could already be
unreachable. After 2017-10-30 00:00 UTC your instance, which has an
EBS volume as the root device, will be stopped.

You can see more information on your instances that are scheduled for
retirement in the AWS Management Console
(https://console.aws.amazon.com/ec2/v2/home?region=us-east-1#Events)

* How does this affect you?
Your instance's root device is an EBS volume and the instance will be
stopped after the specified retirement date. You can start it again at
any time. Note that if you have EC2 instance store volumes attached to
the instance, any data on these volumes will be lost when the instance
is stopped or terminated as these volumes are physically attached to
the host computer

* What do you need to do?
You may still be able to access the instance. We recommend that you
replace the instance by creating an AMI of your instance and launch a
new instance from the AMI. For more information please see Amazon
Machine Images (http://docs.aws.amazon.com/AWSEC2/latest/UserGuide/AMIs.html)
in the EC2 User Guide. In case of difficulties stopping your
EBS-backed instance, please see the Instance FAQ
(http://aws.amazon.com/instance-help/#ebs-stuck-stopping).

* Why retirement?
AWS may schedule instances for retirement in cases where there is an
unrecoverable issue with the underlying hardware. For more information
about scheduled retirement events please see the EC2 user guide
(http://docs.aws.amazon.com/AWSEC2/latest/UserGuide/instance-retirement.html).
To avoid single points of failure within critical applications, please
refer to our architecture center for more information on implementing
fault-tolerant architectures: http://aws.amazon.com/architecture

LZ

On Thu, Oct 26, 2017 at 1:51 PM, Eric D Helms  wrote:
> Our Koji is currently down from a web perspective and ssh access. Please
> don't merge anything further to -packaging until we've resolved this. All
> actions requiring Koji repositories for testing or actions in Koji cannot be
> performed.
>
> If Bryan or Lukas (since I am not sure who has AWS access to the box) could
> investigate for us please.
>
> --
> Eric D. Helms
> Red Hat Engineering
>
> --
> 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.



-- 
Later,
  Lukas @lzap Zapletal

-- 
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] Jenkins can now send email

[Lukas Zapletal]

Greg, thanks for doing this. Now, honestly I do not understand a
single paragraph here.

Can you show me an example JJB patch how to enable this for a plugin?
Ideally discovery, with my spam eating lzap+...@redhat.com :-)

LZ

On Thu, Oct 26, 2017 at 2:21 PM, Greg Sutcliffe  wrote:
> On Thu, 2017-10-26 at 12:58 +0100, Greg Sutcliffe wrote:
>> I have enabled it, but I can't just see where to add this to my user.
>> Perhaps someone with better eyes can spot it. If it works it will
>> remove the need to update JJB so frequently (only for the permenent,
>> important notifications).
>
> As is always the case, I found it right after hitting send ;)
>
> So, there will be some JJB config - the job does need an "Editable
> Email Notification" post-build action adding. However, unless required,
> you can delete all the triggers - simply having the action there is
> enough.
>
> Once that's done, the main page of the job has a "Watch Job" link which
> you can use to add a notify for yourself of results from that job.
>
> One thing I'm seeing is that notifications appear to be in some way
> shared across jobs - adding "On failure" to job1, and then "On
> success"£ to job2, I see "On success" on job1. If that's more than just
> a visual bug, this may not be usable - in which case we can fall back
> on JJB config anyway. Test and feedback please :)
>
> 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.



-- 
Later,
  Lukas @lzap Zapletal

-- 
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] Jenkins can now send email

[Greg Sutcliffe]

On Thu, 2017-10-26 at 12:58 +0100, Greg Sutcliffe wrote:
> I have enabled it, but I can't just see where to add this to my user.
> Perhaps someone with better eyes can spot it. If it works it will
> remove the need to update JJB so frequently (only for the permenent,
> important notifications).

As is always the case, I found it right after hitting send ;)

So, there will be some JJB config - the job does need an "Editable
Email Notification" post-build action adding. However, unless required,
you can delete all the triggers - simply having the action there is
enough.

Once that's done, the main page of the job has a "Watch Job" link which
you can use to add a notify for yourself of results from that job.

One thing I'm seeing is that notifications appear to be in some way
shared across jobs - adding "On failure" to job1, and then "On
success"£ to job2, I see "On success" on job1. If that's more than just
a visual bug, this may not be usable - in which case we can fall back
on JJB config anyway. Test and feedback please :)

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

Re: [foreman-dev] Jenkins can now send email

[Greg Sutcliffe]

Apparently Jenkins could send email before, but I was unaware of it, so
sorry if I confused anyone there. In any case, the sending is a little
clearer now as a result of my changes (hat tip to Eric for the info).

Apparently users should also be able to create their own email
notifications. From the tooltip on the config page:

"Enabling watching allows individual users to add their own triggers to
jobs. The list of triggers they can add is restricted by the trigger
implementer. For example, most script based triggers are not allowed
for users to use as a watch. Users must have READ access to the job in
order to watch it.

Triggers are not stored in the job itself, but as a property on the
user."

I have enabled it, but I can't just see where to add this to my user.
Perhaps someone with better eyes can spot it. If it works it will
remove the need to update JJB so frequently (only for the permenent,
important notifications).

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] Koji Outage

[Eric D Helms]

Our Koji is currently down from a web perspective and ssh access. Please
don't merge anything further to -packaging until we've resolved this. All
actions requiring Koji repositories for testing or actions in Koji cannot
be performed.

If Bryan or Lukas (since I am not sure who has AWS access to the box) could
investigate for us please.

-- 
Eric D. Helms
Red Hat Engineering

-- 
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] Merge rights to Katello installer

[Evgeni Golov]

On Thu, Oct 26, 2017 at 12:03 PM, Ewoud Kohl van Wijngaarden
 wrote:
> On Thu, Oct 26, 2017 at 10:39:28AM +0100, Sean O'Keeffe wrote:
>>
>> I'd like to request write access to the installer team.
>
>
> +1 Sean has shown insight in the modules and the overall picture. His PRs
> are consistently of a high quality.

+1



-- 
Beste Grüße/Kind regards,

Evgeni Golov
Software Engineer

Red Hat GmbH, http://www.de.redhat.com/, Registered seat: Grasbrunn,
Commercial register: Amtsgericht Muenchen, HRB 153243,
Managing Directors: Charles Cachera, Michael Cunningham, Michael
O'Neill, Eric Shander

-- 
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] Matrix.org / IRC bridge

[Greg Sutcliffe]

Hi all,

Over the past week or so I've been trialling Matrix.org[1] as an
alternative to my IRC client. This was partly due to my own curiosity,
and partly because a few people keep suggesting Slack (my objections to
Slack are, I think, well known :P).

Overall I'm pretty impressed with Matrix, at least enough to ask for
more testers. The rooms are "plumbed-in" to the IRC rooms, so it
doesn't matter if you're on Matrix or IRC, you'll see the same content.
(and not via a single account). Indeed, I've been on a Matrix client
for the last week and only a few people have noticed :P. A few other
good points to Matrix:

* Open source (of course :P)
* Federated (our channels are on the main matrix.org server, for now)
* Persistent by default (for all you people without IRC bouncers)
* End-to-end encrypted by default, except plublic rooms
* Plenty of clients (Riot.im is nice, WeeChat plugin for CLI, etc)[2]

The only downside I can see is that only registered IRC users can
private-message a Matrix user - unregistered users get a polite message
about need to register first. This doesn't apply to channels, only PMs.
I don't feel this is too bad, registering to IRC is trivial, and most
support should happen in the channels anyway.

I'll stress that there is *no need* to change anything if you're happy
with IRC, those channels are not going away. But if you've been itching
for something a little more flashy, or just an easy way to have a
persistent connection, Matrix may be of use.

I'm announcing this here before I do it on -users to see if anyone
wants to play / help me find issues. If you do hop on Matrix, I'm
gwmngilfen:matrix.org :)

[1] https://matrix.org/
[2] https://matrix.org/docs/projects/try-matrix-now.html

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] Jenkins can now send email

[Greg Sutcliffe]

Hi all,

In response to a good idea from Lzap about failed plugin builds being
able to email authors, I've enabled SMTP on Jenkins. This is configured
via the Email-Ext plugin [1].

The global config (SMTP auth is done) but for defaults, no triggers are
currently enabled, so that no-one suddenly gets spammed by this. Each
project needs its own config, added as a post-build action. Here's an
example I added ro deploy_web to test:

Add post-build action: Editable Email Notification
Add my email to Project Recipient List
Click Advanced settings
Add "Always" trigger
Set Send To to "Recipient List"

I then rebuilt deploy_web and got the email below :)

However, because this is job config, we'll need to add it to JJB to
stop it being overwritten. Does anyone have a moment to look into
adding it to the JJB files? Then adding authors to plugins for
notifications can be a simple PR.

Enjoy!
Greg

 Forwarded Message 
From: jenk...@theforeman.org
Reply-to: noreply...@theforeman.org
To: 
Subject: deploy_web - Build # 1315 - Successful!
Date: Thu, 26 Oct 2017 09:46:08 + (UTC)

> deploy_web - Build # 1315 - Successful:
> 
> Check console output at http://ci.theforeman.org/job/deploy_web/1315/
>  to view the results.

-- 
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] Merge rights to Katello installer

[Ewoud Kohl van Wijngaarden]

On Thu, Oct 26, 2017 at 10:39:28AM +0100, Sean O'Keeffe wrote:

I'd like to request write access to the installer team.


+1 Sean has shown insight in the modules and the overall picture. His 
PRs are consistently of a high quality.



I've been involved with 38 PRs across what I'd consider to be the 'main'
repos, apparently I created 15 of them and I guess I reviewed the rest.

https://github.com/Katello/puppet-katello/pulls?q=is%3Apr%20involves%3Asean797%20
https://github.com/Katello/katello-installer/pulls?utf8=%E2%9C%93&q=is%3Apr%20involves%3Asean797
https://github.com/Katello/puppet-certs/pulls?utf8=%E2%9C%93&q=is%3Apr%20involves%3Asean797%20
https://github.com/Katello/puppet-candlepin/pulls?utf8=%E2%9C%93&q=is%3Apr%20involves%3Asean797%20
https://github.com/Katello/puppet-foreman_proxy_content/pulls?utf8=%E2%9C%93&q=is%3Apr%20involves%3Asean797
https://github.com/Katello/puppet-pulp/pulls?utf8=%E2%9C%93&q=is%3Apr%20involves%3Asean797%20
https://github.com/Katello/puppet-qpid/pulls?utf8=%E2%9C%93&q=is%3Apr%20involves%3Asean797


--
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] Merge rights to Katello installer

[Sean O'Keeffe]

Hi,

I'd like to request write access to the installer team.

I've been involved with 38 PRs across what I'd consider to be the 'main'
repos, apparently I created 15 of them and I guess I reviewed the rest.

https://github.com/Katello/puppet-katello/pulls?q=is%3Apr%20involves%3Asean797%20
https://github.com/Katello/katello-installer/pulls?utf8=%E2%9C%93&q=is%3Apr%20involves%3Asean797
https://github.com/Katello/puppet-certs/pulls?utf8=%E2%9C%93&q=is%3Apr%20involves%3Asean797%20
https://github.com/Katello/puppet-candlepin/pulls?utf8=%E2%9C%93&q=is%3Apr%20involves%3Asean797%20
https://github.com/Katello/puppet-foreman_proxy_content/pulls?utf8=%E2%9C%93&q=is%3Apr%20involves%3Asean797
https://github.com/Katello/puppet-pulp/pulls?utf8=%E2%9C%93&q=is%3Apr%20involves%3Asean797%20
https://github.com/Katello/puppet-qpid/pulls?utf8=%E2%9C%93&q=is%3Apr%20involves%3Asean797

Thanks,
Sean

-- 
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.