Re: [foreman-dev] Host Creation

2017-02-09 Thread Tom McKay 
I like the "add" buttons (eg. operating system) but there were some
resources that didn't have add buttons (eg. partition tables). Should all
of the associated resources have buttons? Not UX specifically, but it would
also be helpful if the choice lists were made api calls to populate choices
when opened. This way when a resource is added (perhaps on a different
browser page) that resource is selectable without a page refresh (very
painful in current new host ui).

I would also note that it is not uncommon, at least for me, to have the
resource already existing (ie. don't need to create it) but it is either in
the wrong org/loc or missing the association (eg. template not associated
correctly). How would this case be handled?

Highlighting the fields red is great but when does that happen? Is the red
persistent (ie. I leave the wizard and return later)? Having the wizard
step number icons change color would be helpful too. Could be red if error
but maybe some other color/style to indicate that the step is incomplete?

Plugins would need to be able to add/remote steps (eg. ansible), and change
forms. Any UX implications?

Is there a pattern for sub-steps? Step 5, parameters, for example has three
subsections. Would there be cases where each of those lettered sections
have their own pages with a step progress bar? (Not sure if needed.)

After I've created a host, does it become a "template" automatically? I
would like a way to, from a host, go to its wizard and duplicate (could be
just change the name and relaunch, for example).

Overall looks great!




On Wed, Feb 8, 2017 at 3:24 PM, Roxanne Hoover  wrote:

> All -
>
> It was identified amongst users that the Host Creation process could use
> some improvement.
>
> I've come up with a design to help reduce confusion, create a
> clearer/unobstructed path to completion and that also integrates some
> features asked for by users.
>
> I feel the design is complete in terms of the knowledge I posses, and am
> now looking for feedback from the community who I'm sure will have thoughts
> - technical or otherwise -  I hadn't yet considered.
>
> Looking forward to any feedback.
>
>
>
>
> --
> 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] [Event] Foreman Community Demo Items - Thu 16 Feb 3pm [GMT]

2017-02-09 Thread greg . sutcliffe 
Hi all

Demo time! For those who were at the conferences and would like to talk about
things they learned or discussed, please do sign up - perhaps we can do a pnael
of something? For those left behind coding, have a think for items which have
been completed since the last demo on 2017-01-19. There is a query that
will show you items completed (i.e. marked as closed) since the last demo [2].
Please add demo items following the instructions on the agenda page [3].

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

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

Cheers!
--
Greg
IRC: gwmngilfen

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

Fwd: Re: [foreman-dev] candlepin 2.0 merged

2017-02-09 Thread Justin Sherrill 
A new version of candlepin is now available that fixes the upgrade issue 
as well as the manifest reimport issue.


1.  service tomcat stop

2.  yum update 
http://koji.katello.org/packages/candlepin/2.0.25/1.el7/noarch/candlepin-2.0.25-1.el7.noarch.rpm 
http://koji.katello.org/packages/candlepin/2.0.25/1.el7/noarch/candlepin-selinux-2.0.25-1.el7.noarch.rpm 



3.  /usr/share/candlepin/cpdb --update

4.  service tomcat start

5.  update your git checkout to the latest katello master

-Justin




 Forwarded Message 
Subject:Re: [foreman-dev] candlepin 2.0 merged
Date:   Wed, 8 Feb 2017 10:11:47 -0500
From:   Tom McKay 
Reply-To:   foreman-dev@googlegroups.com
To: foreman-dev@googlegroups.com



For visibility:

http://projects.theforeman.org/issues/18424 - [candlepin-2.0] import 
manifest after delete gives: Runtime Error Index: 0, Size: 0 at 
java.util.ArrayList.rangeCheck:653


Error trying to re-import manifest after a deletion

On Tue, Feb 7, 2017 at 6:43 PM, Justin Sherrill > wrote:


   Hi All,

   Candlepin 2.0 has been merged to katello master and available in
   nightly.  Sadly after we merged we found an issue that prevents
   upgrading with all your data in the devel environment.  Until this
   is fixed you'll have to do a full reset:

   1.  systemctl stop tomcat

   2. yum update
   
http://koji.katello.org/packages/candlepin/2.0.24/1.el7/noarch/candlepin-2.0.24-1.el7.noarch.rpm
   

   
http://koji.katello.org/packages/candlepin/2.0.24/1.el7/noarch/candlepin-selinux-2.0.24-1.el7.noarch.rpm
   


   3.  systemctl start tomcat

   4. rake katello:reset   (in your foreman checkout)

   If you don't want to do a full reset you'll need to wait until a
   newer candlepin is available.  I'll send out instructions when a
   fixed build is available. You can stay at commit
   3256117f51f558aa9fd531259cad01200e2576cf and stay on candlepin
   0.9.54 for now.

   If you see any issues please reach out on #theforeman-dev, reply to
   this email, or open an issue.

   Thanks,

   -Justin

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

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