Age | Commit message (Collapse) | Author | Files | Lines |
|
Users can now quickly provision a single-host pod without having to
configure unecessary networking. This is intended to be analogous to the
workflow used during LaaS 1.0, and to speed up the process of creating a
booking for users who do not need more than a single host (for virtual
deployments)
Change-Id: Ia19cea9a42bbb1df57aad05af8f8ea821395664d
Signed-off-by: Sawyer Bergeron <sawyerbergeron@gmail.com>
|
|
Change-Id: I01dd7f671a21c9b9f06dede341d6ddf410f0e776
Signed-off-by: Sawyer Bergeron <sawyerbergeron@gmail.com>
|
|
Users will see a more informative landing page that directs them to log
in if they have not yet done so, rather than displaying actions they can
not yet take and having a required login get triggered later
Change-Id: I9812367930665614933551f780f4c6726ff3049c
Signed-off-by: Sawyer Bergeron <sawyerbergeron@gmail.com>
|
|
|
|
btn-primary has a handful of advantages over btn-default, including
consistency across browsers and correctly styling non-button
html tags
p.s. vim is best
Change-Id: I6e55a75a9fd48d64496fd83f43a7856af0c04cc0
Signed-off-by: Parker Berberian <pberberian@iol.unh.edu>
|
|
Any users that have not uploaded an ssh key will see a message on the
landing page that they need to upload one. Message is not seen by people
who have already uploaded a key
Change-Id: I01667e161521d801090173d47815abbeff094907
Signed-off-by: Sawyer Bergeron <sawyerbergeron@gmail.com>
|
|
A major source of bugs has been how we've approached inlining
workflows. We no longer inline them as of this commit, and instead
use a stack structure. This commits the result of workflows to the
database before other workflows try to read them, so we don't have
to maintain a code path for when something is or isn't committed
to db.
This patchset allows for workflows to pass limited information
to preset selections
Change-Id: I3d040c7f3024c7420017ae4ec66a23219303dcb6
Signed-off-by: Sawyer Bergeron <sawyerbergeron@gmail.com>
|
|
On google chrome, using vanilla html forms, eg:
document.getElementById("Form_id").submit();
does not properly set the CSRF header from the cookies.
This results in 403 unauthorized errors in chrome when doing certain things.
This is possibly an issue to do with how chrome handles iframes differently from firefox.
To fix, we replaced basic forms with serialized XMLHttpRequests,
which are more common in this codebase anyway.
Change-Id: I93e92cd326c8bba47408b66a95d9d5d806c154f6
Signed-off-by: Parker Berberian <pberberian@iol.unh.edu>
|
|
Previously, when a host was 'added' but not given a hostname, it was
excluded from the list of hosts sent to the backend for processing.
By explicitly adding each host to the result, we avoid this and
force the checking of an empty hostname (which will correctly fail).
Change-Id: Ia533bc23baf558a5e297dab629dbf47fb4704d7f
Signed-off-by: Parker Berberian <pberberian@iol.unh.edu>
|
|
See changes here:
https://wiki.opnfv.org/display/INF/Pharos+Laas
Change-Id: I59ada5f98e70a28d7f8c14eab3239597e236ca26
Signed-off-by: Sawyer Bergeron <sbergeron@iol.unh.edu>
Signed-off-by: Parker Berberian <pberberian@iol.unh.edu>
|
|
As subdirectories of the pharos-tools repo, there is little need to keep
the pharos prefix.
Change-Id: Ica3d79411f409df638647300036c0664183c2725
Signed-off-by: Trevor Bramwell <tbramwell@linuxfoundation.org>
|