[foreman-dev] Request to Releasers: Please pull in translations and merge strings

[Bryan Kearney]

This is a request for folks who release plugins, either foreman or hammer.

As part of your release process, please make sure that you are doing the
following:
1) Pulling in the latest translations from transifex
2) Extracting strings from your code, and merging in those translations

Almost all the plugins have a Makefile which will do this for you. If
you got a pull request from me on 1 December, I likely added one or
fixed it. I am happy to answer questions on how to use it, and to help
folks in getting their stuff into transifex (/me is looking at you
foreman-maintain folks).

I have a process which will take translations from downstream and put
them into transifex. This process ensures the community gets the value
of the downstream translators. But, it requires that each time a release
is done the builder refreshes their strings and pulls in the latest
translations.

-- bk

-- 
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 instrumentation for telemetry proposal

[Bryan Kearney]

How would folks disable it opt out of sending this data?

On Nov 20, 2017 9:46 AM, "Lukas Zapletal"  wrote:

> Hey,
>
> on the last demo I presented my proposal for telemetry (it is actually
> a separate video). I am looking for non-intrusive approach with broad
> integration possibilities:
>
> https://www.youtube.com/watch?v=gCLSI9-4QpE
>
> This was also showed on our demo last week (the same content):
> https://www.youtube.com/watch?v=QHzNIFjMpTM
>
> I am starting this thread to gather feedback before I open a PR with
> this. Currently the code is mostly in Rails initializer and looks like
> this:
>
> # get telemetry singleton instance and setup it
> telemetry = Foreman::Telemetry.instance.setup(... some options ...)
>
> # register measurements
> telemetry.add_counter(:http_requests, 'A counter of HTTP requests
> made', [:controller, :action])
> telemetry.add_histogram(:http_request_total_duration, 'Total
> duration', [:controller, :action])
> telemetry.add_counter(:activerecord_instances, 'Number of instances of
> AR models', [:class])
>
> # send measurements from Rails instrumentation or from code base
> telemetry.increment_counter(:http_requests, 1, :controller =>
> controller, :action => action, :status => status)
> telemetry.observe_histogram(:http_request_total_duration, duration,
> :controller => controller, :action => action)
>
> The proposed API is a single class (a singleton actually) with three
> registering methods and three measure methods. I don't think such a
> simple class needs proper separation of concerns, but we can talk
> about this in the PR. The registration part could be turned into some
> kind of DSL, currently it takes metric name, description and list of
> keys which will be part of an instance for those frameworks which do
> not support arbitrary amount of key-value pairs.
>
> If there are no objections, I will add settings and better error
> handling and file the PR.
>
> --
> 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.

[foreman-dev] I am happy to write the headline release notes

[Bryan Kearney]

I would like to know the details of the headline features in 1.16 [1]. I
would be happy to write the text and put int he PR if the authors can
point me at the issues. I can then run it bye you guys for edits.

-- bk


[1] https://theforeman.org/manuals/1.16/index.html#Headlinefeatures

-- 
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] Vendorizing or Building RPMs

[Bryan Kearney]

On 10/16/2017 04:36 AM, Michael Moll wrote:
> I don't really have stakes in RPMs, but I'd try to stick with option 1
> and I even expect that there's some demand for Rails SCLs at least in
> the RHEL/CentOS world by other projects, too.
> 
> Regards

I would suggest the decision be made based on the assumption that the
foreman community owns all the work for options 1 and 2. I have no
special instights, but I would hate to assume we could package based on
another communities work. Assume this commuity owns it all, which way is
better/easier/quicker/less error prone.

-- bk

-- 
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] Turned off autoupdate at transifex

[Bryan Kearney]

I have just re-enabled this.

-- bk


On 10/17/2017 09:51 AM, Lukas Zapletal wrote:
> I would like to know what was the reason to do that. It used to work
> fine for discovery so far.
> 
> I just pushed updated POT into git, I am about to branch off 10.0
> tomorrow. You told me you are going to re-enable this again? Thanks
> 
> LZ
> 
> On Thu, Oct 5, 2017 at 4:18 PM, Lukas Zapletal  wrote:
>> Bryan, I don't understand. Why this was a problem? My understanding is
>> that this feature takes latest and greatest source POT file and puts
>> that for translations.
>>
>> In my workflow, I just pull translations back into PO files when do
>> doing a release. This was a good workflow I think. Or maybe I am
>> missing something.
>>
>> LZ
>>
>> On Thu, Oct 5, 2017 at 2:49 PM, Bryan Kearney  
>> wrote:
>>> I have turned off autoupdatnig of transifex resources. This was a feature
>>> for transifex to pull in the latest stings from github. This would work if
>>> core and all plugin writers are syncing the strings at every release.
>>>
>>> If you release core or a plugin and you are not doing that as part of your
>>> release process can you bug me off line? I would like to make sure that I
>>> did not mess anyone up, and that strings are flowing correctly from project
>>> <-> transifex <-> Red Hat.
>>>
>>> -- bk
>>>
>>> --
>>> 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] Turned off autoupdate at transifex

[Bryan Kearney]

I have turned off autoupdatnig of transifex resources. This was a 
feature for transifex to pull in the latest stings from github. This 
would work if core and all plugin writers are syncing the strings at 
every release.


If you release core or a plugin and you are not doing that as part of 
your release process can you bug me off line? I would like to make sure 
that I did not mess anyone up, and that strings are flowing correctly 
from project <-> transifex <-> Red Hat.


-- bk

--
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 Vertical Navigation Survey

[Bryan Kearney]

On 09/19/2017 08:34 AM, Greg Sutcliffe wrote:

On Tue, 2017-09-19 at 07:42 -0400, Bryan Kearney wrote:


Any chance of seeing the org selector in this demo box?


Apologies - I did enable it after the demo last week, but it appears to
have gotten reset to false while I was fixing other issues. It's back
now.

Greg


Thank you!

-- bk

--
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 Vertical Navigation Survey

[Bryan Kearney]

On 09/19/2017 06:11 AM, Ori Rabin wrote:

Hello all,

The Foreman development team is considering switching to a new, 
vertical-oriented navigation. As this is a big change to the look-n-feel 
of the application, we wanted to consult the community on it.


You can learn more about the reasoning and development of the UI in this 
video (https://www.youtube.com/watch?v=hQwJ11GYfjY) and see it in action 
in this video (https://youtu.be/nZBnQo57Xdc?t=14m33s).


We'd like to invite you to play with the new UI on out demo box 
(https://vertnav.demo.theforeman.org - login "admin" / "vertnav" - 
apologies for the self-signed cert).


Please share your thoughts in the survey: 
https://goo.gl/forms/ERJhphis7Gd85EwJ3





Any chance of seeing the org selector in this demo box?

-- bk

--
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: Release of Foreman Discovery 9.1.2

[Bryan Kearney]

On 09/08/2017 08:01 AM, Lukas Zapletal wrote:

Hello,

new discovery is out in 1.15 repositories (Katello 3.4). We ironed out
few issues around kexec and migration. For more details visit:

http://projects.theforeman.org/projects/13/issues

Have a nice weekend.



QQ on this package. I see it in transifex, but there are two pot files 
in the source code:


fdi.po
foreman_discovery_image.pot


can you please confirm that fdi.pot is not used? It appears not but i 
wanted to confirm before I tied it to downstream.


-- bk

--
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] What is the process to get new resources added to transifex?

[Bryan Kearney]

On 08/31/2017 05:36 AM, Daniel Lobato Garcia wrote:

On 08/30, Bryan Kearney wrote:

I would like to see katello and katello-bastion added to transifex. Once
that is done, I can ask folks to add string syncing to the build process. I
can translate, but I dont have access to add resources.

-- bk


I think you would need to gather the .po files for the projects you want
to add, then upload them to
https://www.transifex.com/foreman/foreman/content/

The administrators at the moment according to
https://www.transifex.com/foreman/public/ are: lzap, ohadlevy, domcleal
mhulan, Claer. They could add the .po files or add you as another
aministrator.



I have these, and I can either supply them or append them to

https://github.com/Katello/katello/pull/6929

which I put in to generate them. I am also happy to beg for admin status.

-- bk

--
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] What is the process to get new resources added to transifex?

[Bryan Kearney]

I would like to see katello and katello-bastion added to transifex. Once 
that is done, I can ask folks to add string syncing to the build 
process. I can translate, but I dont have access to add resources.


-- bk

--
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] Openshift V2 Sunsetting: Redmine and Prprocessor

[Bryan Kearney]

On 08/30/2017 12:25 PM, Greg Sutcliffe wrote:

On Wed, 2017-08-30 at 11:22 -0400, Eric D Helms wrote:

In addition, we realized today that there is another project we
should migrate (and migrate to Foreman proper) the etherpad that is
under the Katello namespace:

http://pad-katello.rhcloud.com


I would expect that to be easy enough, but I have no access to the
katello openshift namespace. Once we've moved the rest we can sync on
getting that migrated.

No word yet on the requested extra resources.

Greg


You all waiting on me?

-- bk

--
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] Syncing F26 external repo on Koji

[Bryan Kearney]

Why stop building against fedora?

On Jul 17, 2017 4:27 PM, "Lukas Zapletal"  wrote:

> Hey,
>
> on pulp team request, I am adding external repository fedora26
> (x86_64) into koji. Initiated the sync, tomorrow I will add that into
> koji external repositories. For the record, I installed mrepo from
> sources as it was not available in EPEL7 anymore.
>
> Foreman core team haven't decided yet if to carry on with building
> against Fedora, version 24 might be the last one. I suggest to
> postpone the final decision until bootstrap in COPR is complete, then
> we can decide.
>
> We can run into space issues quickly on the new koji again as I am
> unable to remove any existing external repo AFAIK. After F26 is
> synced, we still have about 200GB space but that's reserved for our
> builds.
>
> centos6-x86_64
> centos7-x86_64
> epel5-i386
> epel5-x86_64
> epel6-i386
> epel6-x86_64
> epel7-x86_64
> fedora24-x86_64
> fedora25-x86_64
> jpackage-x86_64
> puppetlabsf24-x86_64
> puppetlabs6-x86_64
> puppetlabs7-x86_64
> qpidcopr-i386
> qpidcopr-x86_64
> rhel5-i386
> rhel5-x86_64
> rhel6-i386
> rhel6-x86_64
> rhel7-x86_64
> rhscl-rhel6-x86_64
> rhscl-rhel7-x86_64
>
> --
> 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.

[foreman-dev] How are names of tasks created?

[Bryan Kearney]

There seems to be lots of variaance in the names of tasks, with the 
default adding in the parameters of the tasks. What is the preferred 
pattern for modifying the names?


-- bk

--
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 is back online

[Bryan Kearney]

On 06/14/2017 06:20 AM, Lukas Zapletal wrote:

I haven't noticed builds in multiple (incorrect) tags yet. We will
need to look into that. We do have a koji running from backup (summer
2016) with the last tags from 1.12 release, do you think comparing
these to the new structure and deleting all extra builds would do the
trick?

I assume the fix here is to go look at any package which is tagged into

foreman-nightly-$OS and then remove it from 
foreman-plugins-nightly-$OS. I am not sure about nonscl vs regular rhel 
7. It looks like those are peers so need to be double tagged?


-- bk

--
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: Koji outage on Sunday

[Bryan Kearney]

I am gonna take the optimistic route, and hope that this approach works. 
1.15 should be back up:


foreman-1.15-fedora24
foreman-plugins-1.15-fedora24
foreman-1.15-nonscl-rhel7
foreman-plugins-1.15-nonscl-rhel7
foreman-1.15-rhel7
foreman-plugins-1.15-rhel7

Please kick off some builds against these to let me know if there are 
issues. Jenkins should be usable.


-- bk

On 06/10/2017 03:11 PM, Bryan Kearney wrote:

Update.

Per Lzap's suggestion, I wrote down the rough approach at [1]. I believe 
that foreman-nightly should be ready to test on this machine. 
Specifically, building into these tags:


foreman-nightly-fedora24
foreman-plugins-nightly-fedora24
foreman-nightly-nonscl-rhel7
foreman-plugins-nightly-nonscl-rhel7
foreman-nightly-rhel7
foreman-plugins-nightly-rhel7

There appear to be some issues with passenger which I will need some 
help form folks who know the build process a bit. What I think we need now:


* Test out these targets with foreman nightly builds. Where there are 
failures, please respond with the tasks which have the logs that are 
failing. Jenkins should be set up to run builds. If not, some users are.

* Lzap, is there an easy way to snapshot where the machine is at right now?

-- bk


[1] 
https://docs.google.com/document/d/1909hoztG37oWHyzdSWA4U4M9E8ocrk4qy6a57j3P1FE/edit 



On 06/10/2017 11:25 AM, Lukas Zapletal wrote:

I was trying to rebuild 1.14 in old koji but it did not work well. I
am running into several issues.

Some packages fails to complete build with: GenericError: Unable to
complete build: release mismatch (build: 1.fm1_14.fc24, rpm:
1.fm1_12.fc24) like
http://ec2-54-163-236-166.compute-1.amazonaws.com/koji/taskinfo?taskID=522606 


- I don't  understand, I upload it with fm1_14 tag but it gets rebuild
with fm1_12 and I have no idea where this macro is defined in the
buildroot, I don't see "tfm" package in there. The last "foreman"
package is 1.12, not sure if that matters.

Then when a package gets built, koji fails it to import because there
is already existing file on FS:
http://ec2-54-163-236-166.compute-1.amazonaws.com/koji/taskinfo?taskID=522616 


and I have no idea if that means the package is not added to the
target or it is. Looks like it is ignored.

Also running into other build issues but these are mainly because of
dependencies.

I think that there's no recovery possible from here. One possible use
case for the old koji wold be to bump all package release numbers and
do mass rebuild into nightly so we can get nightlies running. But I
think it can't be used for 1.14 and 1.15 releasing anymore, unless
someone wants to try to fix it.

Now to your newkoji, yes repogen will be always slow even on SSD big
fat box, but it's much better than what we had on the old koji. Now
the trick for massrebuilds is to turn off kojira and trigger
repocreate manually after several packages or when necessary.

The package you link does provide it see down: npm(babel-core) = 6.7.7
so it's the correct dependency. So you are good.



On Sat, Jun 10, 2017 at 5:16 PM, Bryan Kearney 
 wrote:

ok.. I have builds running

http://34.226.218.207/koji/taskinfo?taskID=749

but what i dont get is the build requires. The foreman spec file for 
this

requires npm-babel-core but the package I have

http://34.226.218.207/koji/buildinfo?buildID=15280

provides bundled-npm-babel-core

so something seems off

Aslo merge repos are wicked slow. Lzap, youmentioned setting up dmache?

-- bk


--
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] Re: Koji outage on Sunday

[Bryan Kearney]

Update.

Per Lzap's suggestion, I wrote down the rough approach at [1]. I believe 
that foreman-nightly should be ready to test on this machine. 
Specifically, building into these tags:


foreman-nightly-fedora24
foreman-plugins-nightly-fedora24
foreman-nightly-nonscl-rhel7
foreman-plugins-nightly-nonscl-rhel7
foreman-nightly-rhel7
foreman-plugins-nightly-rhel7

There appear to be some issues with passenger which I will need some 
help form folks who know the build process a bit. What I think we need now:


* Test out these targets with foreman nightly builds. Where there are 
failures, please respond with the tasks which have the logs that are 
failing. Jenkins should be set up to run builds. If not, some users are.

* Lzap, is there an easy way to snapshot where the machine is at right now?

-- bk


[1] 
https://docs.google.com/document/d/1909hoztG37oWHyzdSWA4U4M9E8ocrk4qy6a57j3P1FE/edit


On 06/10/2017 11:25 AM, Lukas Zapletal wrote:

I was trying to rebuild 1.14 in old koji but it did not work well. I
am running into several issues.

Some packages fails to complete build with: GenericError: Unable to
complete build: release mismatch (build: 1.fm1_14.fc24, rpm:
1.fm1_12.fc24) like
http://ec2-54-163-236-166.compute-1.amazonaws.com/koji/taskinfo?taskID=522606
- I don't  understand, I upload it with fm1_14 tag but it gets rebuild
with fm1_12 and I have no idea where this macro is defined in the
buildroot, I don't see "tfm" package in there. The last "foreman"
package is 1.12, not sure if that matters.

Then when a package gets built, koji fails it to import because there
is already existing file on FS:
http://ec2-54-163-236-166.compute-1.amazonaws.com/koji/taskinfo?taskID=522616
and I have no idea if that means the package is not added to the
target or it is. Looks like it is ignored.

Also running into other build issues but these are mainly because of
dependencies.

I think that there's no recovery possible from here. One possible use
case for the old koji wold be to bump all package release numbers and
do mass rebuild into nightly so we can get nightlies running. But I
think it can't be used for 1.14 and 1.15 releasing anymore, unless
someone wants to try to fix it.

Now to your newkoji, yes repogen will be always slow even on SSD big
fat box, but it's much better than what we had on the old koji. Now
the trick for massrebuilds is to turn off kojira and trigger
repocreate manually after several packages or when necessary.

The package you link does provide it see down: npm(babel-core) = 6.7.7
so it's the correct dependency. So you are good.



On Sat, Jun 10, 2017 at 5:16 PM, Bryan Kearney  wrote:

ok.. I have builds running

http://34.226.218.207/koji/taskinfo?taskID=749

but what i dont get is the build requires. The foreman spec file for this
requires npm-babel-core but the package I have

http://34.226.218.207/koji/buildinfo?buildID=15280

provides bundled-npm-babel-core

so something seems off

Aslo merge repos are wicked slow. Lzap, youmentioned setting up dmache?

-- bk


--
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] Re: Koji outage on Sunday

[Bryan Kearney]

ok.. I have builds running

http://34.226.218.207/koji/taskinfo?taskID=749

but what i dont get is the build requires. The foreman spec file for 
this requires npm-babel-core but the package I have


http://34.226.218.207/koji/buildinfo?buildID=15280

provides bundled-npm-babel-core

so something seems off

Aslo merge repos are wicked slow. Lzap, youmentioned setting up dmache?

-- bk

--
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: Koji outage on Sunday

[Bryan Kearney]

e f -name \*.spec | egrep -v
'(foreman|proxy)' | parallel --eta 'pushd $(dirname {}); /usr/bin/tito
release koji-foreman; /usr/bin/tito release koji-foreman-plugins;
popd'

Then regen repos:

koji list-targets --quiet | awk '{print $2}' | sort -u | grep 1.13 |
xargs -n 1 koji regen-repo

Then foreman packages:

mkdir /tmp/tito; find . -type f -name \*.spec | egrep
'(foreman|proxy)' | parallel --eta 'pushd $(dirname {}); /usr/bin/tito
release koji-foreman; /usr/bin/tito release koji-foreman-plugins;
popd'

You will get one package stuck, that is rubygem-locale which fails to
download locale-2.0.9.gem and timeouts for hours. Just skip that for
now.

This is a rough mass rebuild just to test how much feasible is this
path, I will compare meshed repository with what we have.

On Fri, Jun 9, 2017 at 11:54 PM, Lukas Zapletal  wrote:

Also one thought - if your SSD VM is fast enough in building, just
send all packages in a loop and mark first and last task ID, and then
regen repos and resubmit all tasks once again. Those which were built
will not build again (will be red tho but skipped) and those missing
dependencies will build. Repeat several times, N^2 in the worst case
:)

LZ

On Fri, Jun 9, 2017 at 11:50 PM, Lukas Zapletal  wrote:

Bryan I think I found out, turn off kojira service and then you should
not get regens on each successful build!

LZ

On Fri, Jun 9, 2017 at 11:46 PM, Lukas Zapletal  wrote:

Since your clean koji has SSD I can set dmcache for you for the EBS
volume to speed up workload, but I am wrapping up for today, so
tomorrow.

The key is to turn off repo regen after each build, not sure how to do
this. I know it can be done somewhere in configs...

LZ

On Fri, Jun 9, 2017 at 11:43 PM, Lukas Zapletal  wrote:

Basically you go to foreman-packaging rpm/develop and then:

git annex get (few won't download so delete them for now and skip them)

for each package directory (you can do in loop)
tito release koji-foreman
tito release koji-foreman-plugins

First build all packages without "foreman" in it, then regen
buildroots, then all with "foreman" in it and then solve all failed
builds. The order matters.

But I suggest to turn off repo regeneration after each build, I don't
remember how this can be done (anyone?) Then you regenerate at the end
of the build with:

koji list-targets --quiet | awk '{print $2}' | sort -u | egrep
'(foreman|katello|pulp)' | grep nightly | xargs -n 1 koji regen-repo

Also tune your kojibuilder1, I set maxjobs to 7 and capacity to 999 so
it is under nice load of 5-7 concurrent jobs.

On Fri, Jun 9, 2017 at 11:32 PM, Bryan Kearney  wrote:

also.. which rhel7 build is used? scl or nonscl?

-- bk


On 06/09/2017 05:26 PM, Bryan Kearney wrote:


Is there a script to rebuild for nightlies? The tags and external repos
are up and running for nightlies at

http://34.226.218.207/koji/

(cleankoji)

I am planning to reverse-engineer from the composes since I have all the
builds loaded already. But, if there is an easy rebuild that would be great.

-- bk

On 06/09/2017 05:15 PM, Lukas Zapletal wrote:


Quick update. Bryan is working on clean koji installation creating
tags from scratch.

I have koji running from backup, last version built is 1.12. My plan is:

- use our release engineering script to create new 1.13 tags
- regen repos for 1.13 and rebuild all 1.13 packages using tito rebuild
- make a compose and compare that against what we have on
yum.theforeman.org

If this is success, I will do the same for 1.15.

New koji recovered from backup is at
http://ec2-54-163-236-166.compute-1.amazonaws.com/koji/ and we
requested DNS change already, hopefully it's ready on Monday at least
for nightly builds.

On Fri, Jun 9, 2017 at 2:46 PM, Lukas Zapletal  wrote:


Hmmm if I'd have to create new koji I'd rather start from scratch
reimporting our repos back in.

Current problems we had:

- small vm with not enough cores/RAM to run builds
- outdated system (RHEL6) and koji version
- no use of LVM
- data on ephemeral volumes
- lots of symlinks which were added as we grew

If I'd need recreate Koji from scratch, I'd try to avoid all of these.
Local volumes should be only used as cache, swap and temp, external
repos should be on external NFS, everything else on dedicated block
device with regular backups.

On Fri, Jun 9, 2017 at 2:33 PM, Bryan Kearney 
wrote:


On 06/09/2017 08:27 AM, Lukas Zapletal wrote:



I have some bad news to share. I started on moving from our 2nd koji
to 3rd koji created as m1.xxlarge instance so we would avoid NFS and
could run on a single VM. I prepared everything and when I was
shutting down all the builders and test VMs I accidentaly stopped the
2nd koji. Unfortunately the original koji instance was stopped
yesterday as well. We lost all data from epheremal storage volumes,
these were /mnt/tmp holding most importantly Postgres database for

Re: [foreman-dev] Re: Koji outage on Sunday

[Bryan Kearney]

also.. which rhel7 build is used? scl or nonscl?

-- bk

On 06/09/2017 05:26 PM, Bryan Kearney wrote:
Is there a script to rebuild for nightlies? The tags and external repos 
are up and running for nightlies at


http://34.226.218.207/koji/

(cleankoji)

I am planning to reverse-engineer from the composes since I have all the 
builds loaded already. But, if there is an easy rebuild that would be 
great.


-- bk

On 06/09/2017 05:15 PM, Lukas Zapletal wrote:

Quick update. Bryan is working on clean koji installation creating
tags from scratch.

I have koji running from backup, last version built is 1.12. My plan is:

- use our release engineering script to create new 1.13 tags
- regen repos for 1.13 and rebuild all 1.13 packages using tito rebuild
- make a compose and compare that against what we have on 
yum.theforeman.org


If this is success, I will do the same for 1.15.

New koji recovered from backup is at
http://ec2-54-163-236-166.compute-1.amazonaws.com/koji/ and we
requested DNS change already, hopefully it's ready on Monday at least
for nightly builds.

On Fri, Jun 9, 2017 at 2:46 PM, Lukas Zapletal  wrote:

Hmmm if I'd have to create new koji I'd rather start from scratch
reimporting our repos back in.

Current problems we had:

- small vm with not enough cores/RAM to run builds
- outdated system (RHEL6) and koji version
- no use of LVM
- data on ephemeral volumes
- lots of symlinks which were added as we grew

If I'd need recreate Koji from scratch, I'd try to avoid all of these.
Local volumes should be only used as cache, swap and temp, external
repos should be on external NFS, everything else on dedicated block
device with regular backups.

On Fri, Jun 9, 2017 at 2:33 PM, Bryan Kearney 
 wrote:

On 06/09/2017 08:27 AM, Lukas Zapletal wrote:


I have some bad news to share. I started on moving from our 2nd koji
to 3rd koji created as m1.xxlarge instance so we would avoid NFS and
could run on a single VM. I prepared everything and when I was
shutting down all the builders and test VMs I accidentaly stopped the
2nd koji. Unfortunately the original koji instance was stopped
yesterday as well. We lost all data from epheremal storage volumes,
these were /mnt/tmp holding most importantly Postgres database for
kojihub and not sure what else. Our deployment was dozen of symlinks
across two local volumes and EBS.

I found some backups of pgsql on EBS volume, but unfortunately these
stopped being dumped summer 2016
(koji.katello.org-kojidb-20160830-230505.dump is the newest one). Here
are the options we have:

1) Restore the DB and attempt to start services back - but this will
give us instance back with huge gap of almost one year. I am not sure
how much useful that would be - we will not be able to bu ild into
1.15/1.14 repos, missing tags, builds, logs.

2) Move to https://cbs.centos.org CentOS CBS, they run their own Koji
and start building there

3) Speed up Copr transition

4) Build whole new Koji from scratch



A variation here is to use a new DB on the instance we have. So, 
same certs

just a blank DB.

-- bk




--
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] Re: Koji outage on Sunday

[Bryan Kearney]

Is there a script to rebuild for nightlies? The tags and external repos 
are up and running for nightlies at


http://34.226.218.207/koji/

(cleankoji)

I am planning to reverse-engineer from the composes since I have all the 
builds loaded already. But, if there is an easy rebuild that would be great.


-- bk

On 06/09/2017 05:15 PM, Lukas Zapletal wrote:

Quick update. Bryan is working on clean koji installation creating
tags from scratch.

I have koji running from backup, last version built is 1.12. My plan is:

- use our release engineering script to create new 1.13 tags
- regen repos for 1.13 and rebuild all 1.13 packages using tito rebuild
- make a compose and compare that against what we have on yum.theforeman.org

If this is success, I will do the same for 1.15.

New koji recovered from backup is at
http://ec2-54-163-236-166.compute-1.amazonaws.com/koji/ and we
requested DNS change already, hopefully it's ready on Monday at least
for nightly builds.

On Fri, Jun 9, 2017 at 2:46 PM, Lukas Zapletal  wrote:

Hmmm if I'd have to create new koji I'd rather start from scratch
reimporting our repos back in.

Current problems we had:

- small vm with not enough cores/RAM to run builds
- outdated system (RHEL6) and koji version
- no use of LVM
- data on ephemeral volumes
- lots of symlinks which were added as we grew

If I'd need recreate Koji from scratch, I'd try to avoid all of these.
Local volumes should be only used as cache, swap and temp, external
repos should be on external NFS, everything else on dedicated block
device with regular backups.

On Fri, Jun 9, 2017 at 2:33 PM, Bryan Kearney  wrote:

On 06/09/2017 08:27 AM, Lukas Zapletal wrote:


I have some bad news to share. I started on moving from our 2nd koji
to 3rd koji created as m1.xxlarge instance so we would avoid NFS and
could run on a single VM. I prepared everything and when I was
shutting down all the builders and test VMs I accidentaly stopped the
2nd koji. Unfortunately the original koji instance was stopped
yesterday as well. We lost all data from epheremal storage volumes,
these were /mnt/tmp holding most importantly Postgres database for
kojihub and not sure what else. Our deployment was dozen of symlinks
across two local volumes and EBS.

I found some backups of pgsql on EBS volume, but unfortunately these
stopped being dumped summer 2016
(koji.katello.org-kojidb-20160830-230505.dump is the newest one). Here
are the options we have:

1) Restore the DB and attempt to start services back - but this will
give us instance back with huge gap of almost one year. I am not sure
how much useful that would be - we will not be able to bu ild into
1.15/1.14 repos, missing tags, builds, logs.

2) Move to https://cbs.centos.org CentOS CBS, they run their own Koji
and start building there

3) Speed up Copr transition

4) Build whole new Koji from scratch



A variation here is to use a new DB on the instance we have. So, same certs
just a blank DB.

-- bk




--
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] Re: Koji outage on Sunday

[Bryan Kearney]

On 06/09/2017 08:27 AM, Lukas Zapletal wrote:

I have some bad news to share. I started on moving from our 2nd koji
to 3rd koji created as m1.xxlarge instance so we would avoid NFS and
could run on a single VM. I prepared everything and when I was
shutting down all the builders and test VMs I accidentaly stopped the
2nd koji. Unfortunately the original koji instance was stopped
yesterday as well. We lost all data from epheremal storage volumes,
these were /mnt/tmp holding most importantly Postgres database for
kojihub and not sure what else. Our deployment was dozen of symlinks
across two local volumes and EBS.

I found some backups of pgsql on EBS volume, but unfortunately these
stopped being dumped summer 2016
(koji.katello.org-kojidb-20160830-230505.dump is the newest one). Here
are the options we have:

1) Restore the DB and attempt to start services back - but this will
give us instance back with huge gap of almost one year. I am not sure
how much useful that would be - we will not be able to bu ild into
1.15/1.14 repos, missing tags, builds, logs.

2) Move to https://cbs.centos.org CentOS CBS, they run their own Koji
and start building there

3) Speed up Copr transition

4) Build whole new Koji from scratch


A variation here is to use a new DB on the instance we have. So, same 
certs just a blank DB.


-- bk

--
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 3.4 sync time

[Bryan Kearney]

On 05/31/2017 09:23 AM, Lukas Zapletal wrote:

Hello,

with the new release, I performed some tests and it looks like RHEL
7.2 RPM repository (about 11.5k packages) sync with ondemand policy
takes around 40 minutes (download only took few seconds, the rest was
mostly celery and then about 15% was katello reindexing). This is Xeon
v3 bare metal with 10 GB RAM. I haven't compared with 3.3 but this is
sub-par performance. Is this something we will be tackling in the next
release >
Additional syncs is only about minute, so it's really the initial sync
which takes so much time. It is possible that there was no change in
the metadata on the CDN therefore everything was simply skipped. I
will try tomorrow.



How many GB is that repo, and what would the similar times be with curl 
and/or mrepo?


-- bk



--
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] Script to recycle passenger processes

[Bryan Kearney]

On 05/10/2017 05:05 AM, Lukas Zapletal wrote:

Check out the new version I just pushed into the gist! I hope you will like it.

What is the process to go from gist to in 1.16?

-- bk

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

[Bryan Kearney]

On 04/13/2017 03:53 AM, Marek Hulán wrote:

On středa 12. dubna 2017 19:12:32 CEST Bryan Kearney wrote:

On 04/12/2017 09:39 AM, Marek Hulán wrote:

<%= l(report.last_report_at, :format => :long) %>

which prints "April 10, 2017 17:08". The month name and potentially the
format is localized based on current user locale.


What is the effort to make this a user driven setting?
-- bk


I could imagine that as "easy", otoh I'd like to avoid adding more options
just because we're not sure. It's not critical I think. If we chose wrong
format, I'm happy to modify it in next version. Once we have it consistent,
it's easy to grep and change everywhere.

--
Marek

kk.. sounds fair. Perhaps add an abstraction onto it so it can be 
changed in one place?


-- bk

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

[Bryan Kearney]

On 04/12/2017 09:39 AM, Marek Hulán wrote:

<%= l(report.last_report_at, :format => :long) %>

which prints "April 10, 2017 17:08". The month name and potentially the format
is localized based on current user locale.

What is the effort to make this a user driven setting?
-- bk

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

[Bryan Kearney]

On 04/12/2017 11:55 AM, Marek Hulán wrote:

On středa 12. dubna 2017 16:14:36 CEST Bryan Kearney wrote:

+1 on the format

To make sure I am clear:

1) Dates will be stored in the DB as UTC.

yes, but should not matter since the TZ info part of the value and we'd always
convert it according to current user locale


2) Dates will be shown to the user based on their locale.

yes


Questions i have:

a) If I enter a new date, am I entering it in my time zone? Assume
serrver is in UTC +1 and I am in UTC -1. If I enter it in at 23:00 on 12
April, what is stored in the DB?


I'm not sure if we enter the time somewhere. AFACT, rex has some time input
but I'm not sure how it deals with TZs exactly. I think we should use some
time picker in these cases where users would use their TZ and we should
convert it to UTC.


I am thinking scap runs, katello syncplans are hte biggies.




b) What preference/setting controls (2)


go to editting form of your profile
$username in top right corner -> My account
see Timezone field which defaults to "Browser timezone" but can be set to any
time zone



thanks!
-- bk


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

[Bryan Kearney]

+1 on the format

To make sure I am clear:

1) Dates will be stored in the DB as UTC.
2) Dates will be shown to the user based on their locale.

Questions i have:

a) If I enter a new date, am I entering it in my time zone? Assume 
serrver is in UTC +1 and I am in UTC -1. If I enter it in at 23:00 on 12 
April, what is stored in the DB?

b) What preference/setting controls (2)

-- bk


On 04/12/2017 09:39 AM, Marek Hulán wrote:

Hello,

I'd like to suggest one recommended way of displaying date/time information on
all pages. We started a discussion in a PR [1] that would change the format
for config reports, please take a look there for possible solutions.

After a discussion with Roxanne (cc) on another page we agreed on following
form to be the best "April 10, 2017 17:08". So no timezone, no seconds, time
is localized in current user timezone. Users can quickly see how long it was
before so we didn't display the "x y ago" information. We could add it to
tooltip if needed.

Once nice thing about this format is that Rails provide helper to generate it.
One could use something like

<%= l(report.last_report_at, :format => :long) %>

which prints "April 10, 2017 17:08". The month name and potentially the format
is localized based on current user locale.

So before I start sending PRs to various places, I'd like to know if we can
all agree on one form, ideally the suggested one, and try to use it where it
make sense. Please vote either in here or in the linked PR.

The list of various places and formats in Foreman and plugins:

* Core *
reports page - reported at column: "about 1 month ago"
dashboard page: "Generated at 12 Apr 12:41"
facts - reported at columns: "about 1 year ago"
trends page: "Last updated 1 day ago"
audit: "about 1 hour ago" with tooltip saying "April 12, 2017 11:25"
hosts - last report column: 2 months ago
smart proxy - logs - time column: "11. 4. 2017 18:52:31"
smart proxy - puppet ca - ca certificate expiry date: "in almost 4 years"

* Plugins*
discovery - last facts upload: "1 day ago"
openscap reports: "about 1 month ago"
tasks - task details info: "2 minutes ago" with tooltip "2017-04-12 12:49:00
UTC"
rex - jobs: "about 19 hours ago"
rex - logs: "2017-04-11 19:48:09 +0200"
katello - last checking, registered at: "2017-04-12 11:42:06 UTC"
katello - content host tasks: 4/12/17 1:42 PM

Katello would probably need to implement the rails helper (or whatever format
we chose) in their UI helpers. Hopefully that's something easy to do.

[1] https://github.com/theforeman/foreman/pull/4419#issue-217527751

Thanks for reading and sorry for the long email

--
Marek



--
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] Notifications API & UI available - quick HOWTO

[Bryan Kearney]

On 01/23/2017 12:42 PM, Tom McKay wrote:

Wish list...

+ Every notification we add to this system should be required to have a
unique ID based on where it is in the code. This ID could be leveraged
for access insights, docs, etc. (Maybe this is already the case?)


+1

-- bk

--
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] Vertical Navigation

[Bryan Kearney]

On 11/22/2016 09:05 AM, Ohad Levy wrote:



On Tue, Nov 22, 2016 at 3:57 PM, Walden Raines mailto:wal...@redhat.com>> wrote:

+1 I'm a fan of switching to a vertical navigation but I do have one
question.

Is there a pattern for being able to collapse the vertical
navigation?  At times you don't need the navigation at all and it
takes up roughly 1/6th of the screen (as opposed to roughtly 1/10th
with the current horizontal navigation) so it would be nice if it
could be minimized to the side until needed.


is there an assumption we should move to full width with this change?

thanks!
Ohad


+1

-- bk

--
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] Diploma projects - need ideas

[Bryan Kearney]

On 09/29/2016 11:57 AM, Lukas Zapletal wrote:

Hello,

few students of mine are considering doing Diploma Thesis for Red Hat.
Can you figure out some good Foreman topics? Unfortunately, it looks
like today UNIX and datacenter administration is uncool, as I have
learned the other day, so ideally they are looking for:

- JavaScript and UI/UX
- web app development in general
- mobile programming
- iOS / macOS / Swift (need to google that one out)

Ideal task is something isolated, that can be done as a different
project or plugin. Send me your ideas, thanks!


Some ideas I can think of...

* New Auditing/Event framework within the core and plugins. Use cases 
could be:

** I would like to see everything a user did last week
** I would like to see everything done to a host
** I would like to get an alert (text, sms, email) when a host goes red 
** I would like to get an alert (text, sms, email) when XXX conditions 
are met
** I would like to kick off a job in another system when an XXX event 
happen in foreman


* Addition of tags to allow for static groups, and remote actions 
against those groups. Probably some normalization around bookmarks with 
this.


* I dont know if a mobile app makes sense, but some anlaysis/work around 
scaling the app down to a mobile-friendly web page. The use case would 
be checking the status of my network when I am just on my smart phone.


A question I would have out to the community, what type of 
reports/graphs/dashboards do your bosses like to see? Is there some sort 
of visualization that, if included with the tool, would be useful for 
you to have? This type of graph/eye candy may be good ideas here.


Maybe, something akin to:

Draw out the server, smart proxy, and all services. So I can generate a 
picuture which shows this box has the server, which talk to that box 
with the proxy, which in turn communicates with a DHCP server at XXX.


--bk






--
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@googlegroups.com

[Bryan Kearney]

On 09/13/2016 08:01 PM, Partha Aji wrote:


I ve updated the host creation part to work with Katello.

Hostgroup creation is blocked by ->
http://projects.theforeman.org/issues/16532

On Tue, Sep 13, 2016 at 2:35 PM, Tom McKay mailto:thomasmc...@redhat.com>> wrote:

The media selection is unusable on host and host group creation
forms in nightly[1]. I assume foreman-1.13 w/ katello is similarly
broken. @partha is trying to fix it but if a foreman dev familiar
with the UI webpack changes that are the root can help out, that
would be much appreciated. I don't know if bare foreman has issues
but failing to provision out of katello is a blocker.

[1] http://projects.theforeman.org/issues/16480


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

Is there an automated test that caught this?

-- bk

--
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] Expanding Slave Capacity

[Bryan Kearney]

On 08/31/2016 09:30 AM, Dominic Cleal wrote:

On 31/08/16 14:30, Bryan Kearney wrote:

On 08/31/2016 09:07 AM, Dominic Cleal wrote:

On 31/08/16 14:04, Bryan Kearney wrote:

On 08/31/2016 04:09 AM, Dominic Cleal wrote:

On 30/08/16 20:54, Josh Baird wrote:

I would be willing to donate a second slave if necessary.


Thanks for the offer, I'd gladly take you up on it.

Similar specs to the current one would be great, but more disk space if
possible - the usage is increasing.
http://projects.theforeman.org/projects/foreman/wiki/Jenkins#Slave-requirements
lists current specs.

A regular EL7 installation with my SSH key
(https://m0dlx.com/ssh_redhat.pub) installed for root would be enough
for me to set it up.


Would an m3.medium from ec2 be helpful?


If additional storage is available, yes, as the requirements (link
above) are for a minimum of 60GB space, not the 4GB it appears that the
m3.medium spec has.


I mis read that. Are any of the slaves ec2 now? If so, do you know the size?


No, not to my knowledge.


Lets try one:

ec2-184-72-89-17.compute-1.amazonaws.com

your ssh key should work

-- bk

--
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] Expanding Slave Capacity

[Bryan Kearney]

On 08/31/2016 09:07 AM, Dominic Cleal wrote:

On 31/08/16 14:04, Bryan Kearney wrote:

On 08/31/2016 04:09 AM, Dominic Cleal wrote:

On 30/08/16 20:54, Josh Baird wrote:

I would be willing to donate a second slave if necessary.


Thanks for the offer, I'd gladly take you up on it.

Similar specs to the current one would be great, but more disk space if
possible - the usage is increasing.
http://projects.theforeman.org/projects/foreman/wiki/Jenkins#Slave-requirements
lists current specs.

A regular EL7 installation with my SSH key
(https://m0dlx.com/ssh_redhat.pub) installed for root would be enough
for me to set it up.


Would an m3.medium from ec2 be helpful?


If additional storage is available, yes, as the requirements (link
above) are for a minimum of 60GB space, not the 4GB it appears that the
m3.medium spec has.


I mis read that. Are any of the slaves ec2 now? If so, do you know the size?

-- bk

--
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] Expanding Slave Capacity

[Bryan Kearney]

On 08/31/2016 04:09 AM, Dominic Cleal wrote:

On 30/08/16 20:54, Josh Baird wrote:

I would be willing to donate a second slave if necessary.


Thanks for the offer, I'd gladly take you up on it.

Similar specs to the current one would be great, but more disk space if
possible - the usage is increasing.
http://projects.theforeman.org/projects/foreman/wiki/Jenkins#Slave-requirements
lists current specs.

A regular EL7 installation with my SSH key
(https://m0dlx.com/ssh_redhat.pub) installed for root would be enough
for me to set it up.


Would an m3.medium from ec2 be helpful?

-- bk

--
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] Request to have some projects added to transifex

[Bryan Kearney]

On 08/26/2016 02:54 AM, Dominic Cleal wrote:

On 25/08/16 18:26, Bryan Kearney wrote:

Can someone with transifex admin persmission please load the follow
resources into transifex? I am happy to do the leg work, but I have no
mojo :)


https://github.com/theforeman/foreman_ansible/tree/master/locale


Two strings have trailing whitespace that should be replaced by
interpolation of the list of roles/hosts, and they should probably say
"in background":

msgid "Ansible roles running on background: "
msgid "Ansible roles running on background for hosts: "


Added https://github.com/theforeman/foreman_ansible/pull/41 for this.




https://github.com/theforeman/foreman_cockpit/tree/master/locale


Uploaded.


https://github.com/theforeman/hammer-cli-foreman-admin/tree/master/locale


Uploaded.


Thanks^2.
-- bk


--
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] Request to have some projects added to transifex

[Bryan Kearney]

Can someone with transifex admin persmission please load the follow 
resources into transifex? I am happy to do the leg work, but I have no 
mojo :)



https://github.com/theforeman/foreman_ansible/tree/master/locale
https://github.com/theforeman/foreman_cockpit/tree/master/locale
https://github.com/theforeman/hammer-cli-foreman-admin/tree/master/locale

Thanks!

-- bk

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

[Bryan Kearney]

Is there a way to unlock the api a bit more for developers? In 
partcular, I am looking for something which allows me to read the 
categories for a project? Looking at the code, it would be unlocking 
:index on the issue categories controller.


-- bk

--
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] Pushed downstream translations to Transifex

[Bryan Kearney]

This is a followup to the ConfigCamp discussion on translations.

During the Satellite 6.2 release, Red Hat engaged a set of professional 
translators to localize the application. This was done in an internal 
instance of Zanata, and therefore not available to the community. During 
ConfigCamp we analyzed Zanata, and felt it would be a step back and 
therefore did not suggest moving all translations. Instead, we worked on 
some scripts to load strings directly into Transifex. This would allow 
the normal translation process to occur, and the strings would get 
pulled in when appropriate.


I have loaded in all translations from the internal Zanata instance into 
Transifex. These are marked as "unreviewed" so you can use Transifex to 
review the changes.


I have not yet loaded any changed translations into transifex. You can 
see the changes at [1]. There is one diff file per language. I would 
like to give folks a week (until 5 August) to review before I push them 
in. If folks can not do this, the strings would still be marked as 
unreviewed so the tool can be used to find the changes.


Please let me know if you have comments on the process, or if you have 
concerns with the changed translations. I can send along the individual 
diff files if that would help (they are not diff format).


Also, if anyone who has the ability to post notifications to Transifex 
could add this there I would appreciate it.


-- bk

[1] https://gist.github.com/bkearney/3c22b57d19656b04e1b10387e0b5452a

--
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] Thank you from the Satellite Team

[Bryan Kearney]

Foreman Community:

Today Red Hat released Satellite 6.2. The official press release will go 
out tomorrow, but you can read about the release at [1]. This version of 
Satellite is based off of Foreman 1.11 and several of the plugins. The 
success of Red Hat Satellite is based on the hard work and collaboration 
of the Foreman Community. We appreciate all your effort, and are proud 
to be members of the community. Thank you for all the work, and we look 
forward to a successful 1.13!


-- bk

Bryan Kearney
Satellite Team
bkear...@redhat.com


[1] https://access.redhat.com/blogs/1169563/posts/2464761

--
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 integration question

[Bryan Kearney]

On 07/26/2016 02:52 PM, Partha Aji wrote:


Not sure who is working on the Ansible Integration story, do we know if
we plan to serve and manage ansible playbook recipes via pulp similar to
the way we do Puppet Modules?

Partha



Long term yes, short term, no.

- bk


--
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 command line interface/hammer supplement

[Bryan Kearney]

To add a little bit of color, we are launching the RedHatSatellite 
github org to try and encourage customers and field people to contribute 
their scripts. Since these scripts may be branded Satellite or may 
require a specific set of plugins, it seemed like a better place to 
collect them. As submissios come in, if they can easily be made more 
generic we will work to get them into the upstream projects for a 
broader  distribution.


-- bk


On 06/15/2016 02:39 AM, Yoram Hekma wrote:

Hey all,

I just wanted to show you all a project I and a colleague of mine have
been working on and has just been added to the "official" Red Hat
supplemental scripts group on Github. You can find it
at https://github.com/RedHatSatellite/ballista

Ballista is a tool (so far) primarily aimed at Katello and aims to be a
supplement to hammer. It started as a tool to recursively publish
content views and their composites, but it has started growing into a
more modularized (?) thing that is easily extendable via modules. The
documentation is not yet up to snuff, but it is actively maintained (and
used in production environments) and pull requests are always welcome.

Cheers,
Yoram

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