[foreman-dev] Re: Etherpad Back Online (Sorta)

[Eric D Helms]

I was a bit pre-mature. There is no sorta! I upgraded the storage just
enough to let me fully restore the database. You should find anything as of
Sunday available on it now. If something is missing please let me know. But
for all intents and purposes, consider this up and running now.

Eric

On Tue, Oct 3, 2017 at 3:40 PM, Eric D Helms  wrote:

> All,
>
> Openshift V2 sunsetting caused out normal etherpad to go down. I've been
> able to partially restore it on our still running V2 account. I was able to
> what I can surmise as partially restore the database, so if you had prior
> pads with data you need that may or may not exist on it. The partial
> restore is due to how much space mongodb consumes when restoring a database
> and the limited size of the V2 gear. We still have the original mongodb
> that can still be restored on other hardware or setup to recover any data
> that users may need. For now, if you need a scratch etherpad feel free to
> use this but please don't use it as long term storage. Prefer instead to
> use it for collaboration and move off anything you need to store to -dev
> mailing list or wiki for now.
>
> http://pad-theforeman.rhcloud.com/
>
> --
> Eric D. Helms
> Red Hat Engineering
>



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

[foreman-dev] Etherpad Back Online (Sorta)

[Eric D Helms]

All,

Openshift V2 sunsetting caused out normal etherpad to go down. I've been
able to partially restore it on our still running V2 account. I was able to
what I can surmise as partially restore the database, so if you had prior
pads with data you need that may or may not exist on it. The partial
restore is due to how much space mongodb consumes when restoring a database
and the limited size of the V2 gear. We still have the original mongodb
that can still be restored on other hardware or setup to recover any data
that users may need. For now, if you need a scratch etherpad feel free to
use this but please don't use it as long term storage. Prefer instead to
use it for collaboration and move off anything you need to store to -dev
mailing list or wiki for now.

http://pad-theforeman.rhcloud.com/

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

[foreman-dev] Webpack build time

[Umesh Sharma]

Hi,

I am using webpack to build my react project in production. As my project 
is getting bigger its taking too much time to build which results in 
downtime of my website. Can i configure webpack in such a way that it 
builds and replaces the old compiled js files. 

Thanks
Umesh 

-- 




Explore. Express. Earn Rewards.
India's Best Experience Discovery App
1 Million+ Users | 10 cities
Android  
| iOS 
 
| Windows 




*Check Out Bangalore's Best Restaurants 
*

-- 
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] Form inputs and accessibility

[Walden Raines]

I don't know that we want randomized IDs as that doesn't really help QE
any.  Ideally we'd have purposefully chosen unique IDs so that we meet both
goals here:

1. Accessibility for the visually impared
2. Simplifying QE automation testing

Cheers,
Walden

On Mon, Oct 2, 2017 at 10:38 AM, Lukas Zapletal  wrote:

> I think there was a patch that added randomized IDs to all elements
> which were missing it. I think it did not get it through review.
>
> LZ
>
> On Sat, Sep 30, 2017 at 6:33 PM, Ohad Levy  wrote:
> >
> >
> > On Fri, Sep 29, 2017 at 7:16 PM, Walden Raines 
> wrote:
> >>
> >> Hey everyone,
> >>
> >> I would like to propose that we establish a requirement that all new
> form
> >> inputs include both a unique ID attribute and a  like so:
> >>
> >> Name:
> >> 
> >>
> >> For form fields where the is no label we should use bootstrap's .sr-only
> >> class on the label to hide it like so:
> >>
> >> Name:
> >> 
> >>
> >> This allows screen readers to relate a label field to an input in a
> >> meaningful way making it easier for the visually impaired to use our
> >> application (as an added bonus unique input IDs also allow for easier to
> >> write and maintain QA automation).  It is important that the ID be
> unique to
> >> the page so as not to confuse screen readers and also in order to
> produce
> >> valid HTML.
> >>
> >> Please help this effort by keeping an eye out for new input fields that
> >> on't have IDs and labels and if you happen to notice an input without
> an ID
> >> and label please fix it.
> >
> > In foreman, its all going though a single code path, so a simple change
> to
> >>
> >>
> >> https://github.com/theforeman/foreman/blob/develop/app/
> helpers/form_helper.rb#L326
> >> will get what you are looking for.
> >> See also [1].
> >>
> >> Thanks,
> >> Walden
> >>
> >> [1] https://webaim.org/techniques/forms/controls#input
> >>
> >> --
> >> 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.
>

-- 
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: Re: [foreman-dev] unscheduled 1.15.5

[Ondrej Prazak]

@lzap: Yes, it is container-related. I opened [1] that should go in there,
correct me if I missed something. Thanks for letting me know about the DHCP
issue.


[1] https://github.com/theforeman/foreman-selinux/pull/71

On Tue, Oct 3, 2017 at 12:38 PM, Ewoud Kohl van Wijngaarden <
ew...@kohlvanwijngaarden.nl> wrote:

> That's only part of it. These are still open:
>
> Fix issues on EL7.4:
> * https://github.com/theforeman/puppet-foreman_proxy/pull/376
> * https://github.com/theforeman/puppet-foreman_proxy/pull/377
>
> Fix OpenSCAP on Puppet 4 systems:
> * https://github.com/theforeman/puppet-puppet/pull/554
>
> Once those are merged I'll create releases and update the installer. These
> also fix issues downstream.
>
>
> On Tue, Oct 03, 2017 at 12:26:07PM +0200, Daniel Lobato Garcia wrote:
>
>> Similarly I think the installer is meant to be updated to work with 7.4
>> - https://github.com/theforeman/foreman-installer/commit/f0756
>> 7ee06742155a079f076823c6a3bfbc38120
>>
>> On 10/03, Lukas Zapletal wrote:
>>
>>> Ondra,
>>>
>>> what fixes are you talking about? Is this the container selinux
>>> installation issue?
>>>
>>> If there is a chance of sneaking in
>>>
>>> https://github.com/theforeman/foreman/pull/4555
>>>
>>> if this is merged in the deadline, that would be great. Pretty
>>> important provisioning DHCP issue there.
>>>
>>> LZ
>>>
>>> On Tue, Oct 3, 2017 at 10:35 AM, Ondrej Prazak 
>>> wrote:
>>> > Hi,
>>> > there will be a 1.15.5 Foreman release. Main motivation behind this is
>>> to
>>> > get SELinux fixes into 1.15, but if you are aware of any critical fix
>>> that
>>> > should go in there, let me know.
>>> >
>>> > Have a nice day,
>>> > Ondrej Prazak
>>>
>>
> --
> 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: Re: [foreman-dev] unscheduled 1.15.5

[Ewoud Kohl van Wijngaarden]

That's only part of it. These are still open:

Fix issues on EL7.4:
* https://github.com/theforeman/puppet-foreman_proxy/pull/376
* https://github.com/theforeman/puppet-foreman_proxy/pull/377

Fix OpenSCAP on Puppet 4 systems:
* https://github.com/theforeman/puppet-puppet/pull/554

Once those are merged I'll create releases and update the installer. 
These also fix issues downstream.


On Tue, Oct 03, 2017 at 12:26:07PM +0200, Daniel Lobato Garcia wrote:

Similarly I think the installer is meant to be updated to work with 7.4
- 
https://github.com/theforeman/foreman-installer/commit/f07567ee06742155a079f076823c6a3bfbc38120

On 10/03, Lukas Zapletal wrote:

Ondra,

what fixes are you talking about? Is this the container selinux
installation issue?

If there is a chance of sneaking in

https://github.com/theforeman/foreman/pull/4555

if this is merged in the deadline, that would be great. Pretty
important provisioning DHCP issue there.

LZ

On Tue, Oct 3, 2017 at 10:35 AM, Ondrej Prazak  wrote:
> Hi,
> there will be a 1.15.5 Foreman release. Main motivation behind this is to
> get SELinux fixes into 1.15, but if you are aware of any critical fix that
> should go in there, let me know.
>
> Have a nice day,
> Ondrej Prazak


--
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: Re: [foreman-dev] unscheduled 1.15.5

[Daniel Lobato Garcia]

Similarly I think the installer is meant to be updated to work with 7.4
- 
https://github.com/theforeman/foreman-installer/commit/f07567ee06742155a079f076823c6a3bfbc38120

On 10/03, Lukas Zapletal wrote:
> Ondra,
>
> what fixes are you talking about? Is this the container selinux
> installation issue?
>
> If there is a chance of sneaking in
>
> https://github.com/theforeman/foreman/pull/4555
>
> if this is merged in the deadline, that would be great. Pretty
> important provisioning DHCP issue there.
>
> LZ
>
> On Tue, Oct 3, 2017 at 10:35 AM, Ondrej Prazak  wrote:
> > Hi,
> > there will be a 1.15.5 Foreman release. Main motivation behind this is to
> > get SELinux fixes into 1.15, but if you are aware of any critical fix that
> > should go in there, let me know.
> >
> > Have a nice day,
> > Ondrej Prazak
> >
> > --
> > 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.

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


signature.asc
Description: PGP signature

Re: Re: [foreman-dev] Release process & permissions

[Daniel Lobato Garcia]

On 09/28, Ewoud Kohl van Wijngaarden wrote:
> While I agree we should automate a lot, I agree with Eric. Doing a Foreman
> release should involve a human to keep the end-to-end quality. Just giving
> permissions is wrong.
>
> For example in Foreman 1.15.5 the installer was tagged and released before I
> could push in my changes. That communication failure might have been partly
> my fault but IMHO the job of a release manager is to communicate with all
> the maintainers if everything is in place for a release.
>
> Now you state it as a problem that you need a lot of people, but you need to
> communicate with them anyway. Yes, the tagging and releasing should be
> scripted but planning a release will require humans.
>
> Like Eric I think we should start by documenting. Right now it's a huge
> black box for most people, let's start there.

The process is pretty well documented,
http://projects.theforeman.org/projects/foreman/wiki/Release_Process
contains everything that has to be done step by step

>
> On Wed, Sep 27, 2017 at 09:19:10PM -0400, Eric D Helms wrote:
> > There are two considerations that I'd like to put forth as we think about
> > this:
> >
> > 1) Instead of adding jobs, we re-think and re-write the release job in
> > Pipeline syntax similar to my starter here --
> > https://github.com/theforeman/foreman-infra/pull/323
> > 2) We don't automate all the things as there are some tasks that should be
> > done by a human. The tedious, repetitive bits we should automate. The
> > aspects that require some human foresight, approval or double checking of
> > we should either require a releaser to "yes" to a job over or to perform
> > semi-automated in that the user uses tooling but ultimately has input. For
> > example, cherry picking should be 90% automated but 10% human input to
> > ensure nothing seems off since our issue-to-change is not flawless.
> >
> > While we have some automation already in place, from my experience I would
> > recommend one of the following approaches.
> >
> > 1) create a flow chart of every action that has to happen using something
> > like plantuml with parallel actions where possible
> > 2) Create a new release job, starting either from the beginning or the end
> > of the process and add each next step to it
> >
> >
> > Eric
> >
> > On Wed, Sep 27, 2017 at 10:46 AM, Daniel Lobato Garcia 
> > wrote:
> >
> > > Hi devs,
> > >
> > > After a few releases, and now that I'm trying to help someone else to
> > > take over in case it's needed, I found a roadblock.
> > >
> > > Whoever is doing the release, needs to have **many** permissions.
> > >
> > > Otherwise, it doesn't make much sense for a person to take over release
> > > responsibilities. For example, if Ondrej has to do 1.15.5, he would need
> > > the following permissions (see at the end of the email).
> > >
> > > Of course there are alternatives:
> > >
> > > 1 is to have the release nanny be supervised by people who have 'earned'
> > > these permissions. This is a bad idea because some of the tasks just
> > > cannot be 'supervised'. The nanny would have to ask someone to tag
> > > repositories, modify jenkins jobs, upload GPG signatures, post to the
> > > mailing list, tag new builds in Koji...
> > >
> > > 2 is to extend http://ci.theforeman.org/view/Release%20pipeline/ and
> > > make it a real pipeline from 0 to release completed. At this moment,
> > > releases that are not the first RC1 are mostly automated by
> > > https://github.com/dlobatog/foreman_release and
> > > https://github.com/theforeman/tool_belt.
> > >
> > > My proposal is to go forward with 2. Give Jenkins permissions to do all
> > > of the actions needed, and whoever is the release nanny, ideally only
> > > has to make sure all of the steps are moving forward. If something
> > > breaks, figure out how to fix it for the next release.
> > >
> > > This would mean making a few extra jobs before and after the current
> > > release pipeline. In my opinion, it's the way to go to ensure anyone can
> > > take over this responsibility.
> > >
> > > At this moment, we are in a situation where only people who
> > > mostly have permissions everywhere can successfully do a release without
> > > asking many people for favors.
> > >
> > > Personally if we complete this, I see it as a big win as it would dwarf
> > > our bus factor for release managers & allow us to release at any pace we
> > > desire (right now it's slow because we can't truly release things from
> > > one day to the next due to the work involved).
> > >
> > > Thoughts?
> > >
> > > Here's the list of permissions:
> > >
> > > 
> > >
> > > Github:
> > >   - Push in foreman, foreman-selinux, foreman-installer,
> > > smart-proxy, foreman-infra, foreman-packaging
> > >
> > > Transifex -
> > >   - Allow to change the auto-update URL to point to latest -stable
> > > branch
> > >
> > > Redmine -
> > >   - Create new "Found in Release" version
> > >
> > > Jenkins -
> > >   - Modify jobs
> > > 

Re: [foreman-dev] unscheduled 1.15.5

[Lukas Zapletal]

Ondra,

what fixes are you talking about? Is this the container selinux
installation issue?

If there is a chance of sneaking in

https://github.com/theforeman/foreman/pull/4555

if this is merged in the deadline, that would be great. Pretty
important provisioning DHCP issue there.

LZ

On Tue, Oct 3, 2017 at 10:35 AM, Ondrej Prazak  wrote:
> Hi,
> there will be a 1.15.5 Foreman release. Main motivation behind this is to
> get SELinux fixes into 1.15, but if you are aware of any critical fix that
> should go in there, let me know.
>
> Have a nice day,
> Ondrej Prazak
>
> --
> 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.

[foreman-dev] unscheduled 1.15.5

[Ondrej Prazak]

Hi,
there will be a 1.15.5 Foreman release. Main motivation behind this is to
get SELinux fixes into 1.15, but if you are aware of any critical fix that
should go in there, let me know.

Have a nice day,
Ondrej Prazak

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