Re: Anaconda spoke workflow

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



On Wed, Dec 30, 2015 at 12:49:20PM -0600, Pat Riehecky wrote:
> I'm focusing a bit on my GUI spoke workflow and ran into an odd snag.
> 
> The spoke is optional (@property mandatory = False and @property completed =
> True).
> It only makes sense to manipulate the spoke's data after the network has
> come online.
> If nothing is set on the spoke, this is fine and no actions are performed.
> 
> My initial thoughts were to make @property ready return the value of
> pyanaconda.nm.nm_is_connected().  However, if the network is never connected
> then spoke is never ready and therefore install can never proceed.
> 
> Are there any suggestions for how I can get what I'm looking for where the
> user can't use the spoke without the network but the spoke doesn't block the
> install?
> 
> anaconda-19.31.123

Is there any state where you want the spoke to block the install, or are
you just trying to block entry into the spoke when the network is down?
Looking at the current code I'm not sure there is a way to block spoke
entry for always ready non-mandatory spokes.

-- 
Brian C. Lane | Anaconda Team | IRC: bcl #anaconda | Port Orchard, WA (PST8PDT)

_______________________________________________
Anaconda-devel-list mailing list
Anaconda-devel-list@xxxxxxxxxx
https://www.redhat.com/mailman/listinfo/anaconda-devel-list



[Index of Archives]     [Kickstart]     [Fedora Users]     [Fedora Legacy List]     [Fedora Maintainers]     [Fedora Desktop]     [Fedora SELinux]     [Big List of Linux Books]     [Yosemite News]     [Yosemite Photos]     [KDE Users]     [Fedora Tools]
  Powered by Linux