Re: [foreman-dev] 1.15.0 release status

[Daniel Lobato]

1.15.1 is expected to be released around 2 weeks after .0.
>From what I see the biggest change seems to be
https://github.com/theforeman/foreman-packaging/pull/1627 (for debs)
rpm-wise the changes are not as critical I think, so if they can be
built for 1.15.1
that'd be good, there are 2 weeks of nightlies to test hammer before
the release.

On Tue, May 9, 2017 at 10:55 PM, Tomas Strachota  wrote:
> Since Hammer CLI 0.10.2 contains significant usability improvements
> around ssl certificates (fetching certs without need of root
> permissions) and sessions (retry on expiry) I think that we should
> definitely include it in 1.15.1 if it's not possible to include it in
> 1.15.0.
>
> T.
>
> On Tue, May 9, 2017 at 1:15 PM, Dominic Cleal  wrote:
>> On 09/05/17 12:04, Daniel Lobato wrote:
>>> Our 1.15 release is almost there! Tagging is done. I kicked off the
>>> release pipeline, which means the first release tarballs are on their way.
>>
>> I guess you don't want Hammer CLI 0.10.2 packages to be merged at this
>> point then - do you want them merged after this release for 1.15.1, or
>> do not include it in the 1.15 series?
>>
>> (There were requests at
>> https://github.com/theforeman/foreman-packaging/pull/1641 and 1638 that
>> would have needed your approval. They also require a number of
>> dependency changes/additions.)
>>
>> --
>> Dominic Cleal
>> domi...@cleal.org
>>
>> --
>> 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.



-- 
Daniel Lobato

@dlobatog
daniellobato.me

GPG: http://keys.gnupg.net/pks/lookup?op=get=0x7A92D6DD38D6DE30

-- 
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] vmware html5 console support

[Michael Eklund]

For us, being prompted for a password is not a dealbreaker.  I have a pet 
project to investigate using vcenter SSO for 3rd party logins down the 
line, so that might be something that can benefit foreman as well.

Mike E.

On Tuesday, May 9, 2017 at 4:56:09 AM UTC-5, Timo Goebel wrote:
>
>
> Am Montag, 8. Mai 2017 18:27:58 UTC+2 schrieb Michael Eklund:
>>
>> I would be happy to help with testing.  IMO this is a killer feature.
>>
>
> I created some code to test this. [1] Unfortunately pre-authentication 
> does not work with vsphere > 6 as it always requires SSO.
>
> Great idea, but it does not work.
>
> Timo
>
> [1] https://gist.github.com/timogoebel/c8a915dc4fae9b79c8733cc7a2796038
>

-- 
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] Performance analysis deep-dive, what would you like to hear about?

[Christopher Duryee]

On Tue, May 9, 2017 at 9:01 AM,  wrote:

> Hey, I want to do a performance analysis deep-dive.
>
> What I had in mind:
>
> 1. Installation of tooling in development environment
> 2. Simple request breakdown (view, sql)
> 3. Debugging API request
> 4. Time graph (flamegraph)
> 5. Memory consumption
> 6. Installation in prod env
> 7. Analyzing POST requests
>
> Feel free to ask questions and suggest topics that you want me to cover.
>

This list looks good, thanks for covering it. Can you also add how to check
if a foreman instance is maxed out on passenger workers via
passenger-status?


>
> Shim.
>
> --
> 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] [RFC] Proposal: make foreman STI to work even when an inherited class is not found in Ruby.

[Lukas Zapletal]

Wow this is nice! I did not see this coming...

LZ

On Sun, May 7, 2017 at 3:58 PM, Shimon Shtein  wrote:
>
> OK, it wasn't exactly my intention, but I see the discussion moves towards
> general plugin install/uninstall procedure.
>
> I have discovered a nice feature that enables us to isolate plugin
> migrations, and run them on per-plugin manner:
> Apparently we can run:
> rake db:migrate SCOPE=my_plugin
> rake db:migrate SCOPE=my_plugin VARSION=0 # to migrate down
> And it will run only migrations that are tagged for that scope. One can
> achieve that by generating proper migration names:
> _..rb
> I have added a PR that generates migrations for plugins with the proper
> naming: https://github.com/theforeman/foreman/pull/4509.
>
> This should be the base for complete removal. Then, if we add a down-only
> migration that removes STI's - it should be enough to remove all DB traces
> for a plugin.
>
>
>
> On Wed, May 3, 2017 at 2:11 PM, Lukas Zapletal  wrote:
>>
>> I agree with Tomas, it's more cleaner to remove all the data right
>> away. Therefore I suggest that we check for these kind of objects
>> during initialization and if such an class is (not) found, then we can
>> throw an error like "Run foreman-rake plugin:clean" to delete orhpaned
>> records.
>>
>> I am for (A) - remove all the data.
>>
>> LZ
>>
>> On Wed, May 3, 2017 at 11:16 AM, Tomas Strachota 
>> wrote:
>> > This issue is tightly coupled with plugin uninstallation and I think
>> > we should solve the two problems together. At the moment there's no
>> > standard plugin uninstallation procedure that would take care of
>> > cleaning up the system. This is something each plugin should provide.
>> > One thing (imho the less important in this context) is where we put
>> > such code. Should it be a rake task, part of installer, part of
>> > maintanance script, somewhere else?
>> >
>> > What I see as more important is to decide what data will the
>> > uninstallation process remove (keep all vs. keep only settings vs.
>> > wipe all) and how we want the plugin to behave if it's installed
>> > again. This will affect how we approach missing STI classes.
>> >
>> > I can see 3 options:
>> >
>> > a) Remove all data
>> > Plugin would remove all tables and records it created. In such case we
>> > probably don't need to change the STI behavior. Plugin uninstallation
>> > should take care of removing the data correctly. If it fails it's fine
>> > to throw exception to indicate the system integrity is broken. This
>> > approach is imho safer for us as developers and requires less
>> > defensive coding.
>> >
>> > b) Keep all the data
>> > In this case the original data should be present when the plugin is
>> > installed again. STI records without classes should be completely
>> > hidden in the default scope. If all records are listed we should
>> > return either instances of base class or some special class for the
>> > missing types. I'm afraid this approach is quite fragile and can lead
>> > to many surprises when a plugin is uninstalled, the foreman lives
>> > without it for some time and then you install it again. I'm also not
>> > sure how common is such usecase.
>> >
>> > c) Combination of a) and b)
>> > We can keep data where it's safe (like settings) and delete the rest.
>> >
>> > I'm in favor of a) or c)
>> >
>> > T.
>> >
>> >
>> >
>> >
>> >
>> > On Sun, Apr 30, 2017 at 10:05 AM,   wrote:
>> >>
>> >> Hello,
>> >>
>> >> lately I was switching plugins on and off, and I stumbled upon an
>> >> annoying
>> >> issue: Many plugins that add some STI classes (for example Katello that
>> >> adds
>> >> settings, or Discovery that adds DiscoveredHost).
>> >> A problem starts when such a plugin is removed from the system, since
>> >> default STI implementation will throw an error if it can't load a class
>> >> that
>> >> corresponds to the :type column in the DB.
>> >>
>> >> I propose a custom handling for such cases, since they are not exactly
>> >> exceptions in our system design.
>> >> I was thinking about one of the following options to handle this case,
>> >> and
>> >> would like to see a voting which one you prefer. Of course other
>> >> options can
>> >> be proposed too.
>> >>
>> >> 1. Return a base class for such records (Maybe with an error already
>> >> set)
>> >> 2. Return nil/some kind of special AR object for such records (will
>> >> require
>> >> defensive coding while handling heterogeneous lists)
>> >> 3. Filter those records out with default scope (will require more
>> >> declaration in plugins, or more DB queries on system startup)
>> >>
>> >> Any thoughts in this area will be much appreciated,
>> >>
>> >> Shim
>> >>
>> >> --
>> >> 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] Performance analysis deep-dive, what would you like to hear about?

[sshtein]

Hey, I want to do a performance analysis deep-dive.

What I had in mind:

1. Installation of tooling in development environment
2. Simple request breakdown (view, sql)
3. Debugging API request
4. Time graph (flamegraph)
5. Memory consumption
6. Installation in prod env
7. Analyzing POST requests

Feel free to ask questions and suggest topics that you want me to cover.

Shim.

-- 
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] 1.15.0 release status

[Dominic Cleal]

On 09/05/17 12:04, Daniel Lobato wrote:
> Our 1.15 release is almost there! Tagging is done. I kicked off the
> release pipeline, which means the first release tarballs are on their way. 

I guess you don't want Hammer CLI 0.10.2 packages to be merged at this
point then - do you want them merged after this release for 1.15.1, or
do not include it in the 1.15 series?

(There were requests at
https://github.com/theforeman/foreman-packaging/pull/1641 and 1638 that
would have needed your approval. They also require a number of
dependency changes/additions.)

-- 
Dominic Cleal
domi...@cleal.org

-- 
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] 1.15.0 release status

[Daniel Lobato]

Hi Foreman devs,

Our 1.15 release is almost there! Tagging is done. I kicked off the release
pipeline, which means the first release tarballs are on their way.

After that I will sign them and continue so we can build rpms & debs. As
soon as that's ready I will sign and publish them.

I am boarding a plane now, hopefully when I land the tarballs will be ready
to be signed :) Sorry for the slight delay!

In case something goes wrong let me know on this thread.

Best regards,

-- 
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] How to compute resource

[Adam Ruzicka]

Hello,
the Compue Resource part of How to create a plugin on Foreman's wiki[1]
might be a good place to start. Also taking a look at sources of existing
compute resources and/or plugins adding some might provide a bit of insight.

1 -
http://projects.theforeman.org/projects/foreman/wiki/How_to_Create_a_Plugin#Compute-resources

Hope this helps

Adam

On Tue, May 9, 2017 at 9:33 AM, lovi  wrote:

> Hello,
>
> Where could I find the documentation to understand how to create a new
> compute resource ?
>
> Regards
>
> --
> 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] vmware html5 console support

[Timo Goebel]

Am Montag, 8. Mai 2017 18:27:58 UTC+2 schrieb Michael Eklund:
>
> I would be happy to help with testing.  IMO this is a killer feature.
>

I created some code to test this. [1] Unfortunately pre-authentication does 
not work with vsphere > 6 as it always requires SSO.

Great idea, but it does not work.

Timo

[1] https://gist.github.com/timogoebel/c8a915dc4fae9b79c8733cc7a2796038

-- 
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 to compute resource

[lovi]

Hello,

Where could I find the documentation to understand how to create a new 
compute resource ?

Regards

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