Re: [ovirt-users] [ovirt-devel] Cockpit oVirt support

2017-10-19 Thread Marek Libra
Regarding libvirt, there's fallback to Libvirt provider (part of
cockpit-machines) for VMs which are not managed by oVirt.
For the oVirt ones, oVirt API handles all the actions.

It's not yet implemented, but I'm considering to fallback to Libvirt for
selected actions in case the oVirt API can't be reached. Like for shut down
[1].

Anyway, there's still open question with the Libvirt connection since it's
secured on an oVirt host.

[1] https://github.com/cockpit-project/cockpit/issues/7670

On Wed, Oct 18, 2017 at 3:18 PM, Ryan Barry <rba...@redhat.com> wrote:

> This looks great, guys. Congrats!
>
> Does this also work with plain libvirt?
>
> On Wed, Oct 18, 2017 at 3:24 AM, Michal Skrivanek <
> michal.skriva...@redhat.com> wrote:
>
>> Hi all,
>> I’m happy to announce that we finally finished initial contribution of
>> oVirt specific support into the Cockpit management platform
>> See below for more details
>>
>> There are only limited amount of operations you can do at the moment, but
>> it may already be interesting for troubleshooting and simple admin actions
>> where you don’t want to launch the full blown webadmin UI
>>
>> Worth noting that if you were ever intimidated by the complexity of the
>> GWT UI of oVirt portals and it held you back from contributing, please take
>> another look!
>>
>> Thanks,
>> michal
>>
>> Begin forwarded message:
>>
>> *From: *Marek Libra <mli...@redhat.com>
>> *Subject: **Re: Cockpit 153 released*
>> *Date: *17 October 2017 at 16:02:59 GMT+2
>> *To: *Development discussion for the Cockpit Project <
>> cockpit-de...@lists.fedorahosted.org>
>> *Reply-To: *Development discussion for the Cockpit Project <
>> cockpit-de...@lists.fedorahosted.org>
>>
>> Walk-through video for the new "oVirt Machines" page can be found here:
>> https://youtu.be/5i-kshT6c5A
>>
>> On Tue, Oct 17, 2017 at 12:08 PM, Martin Pitt <mp...@redhat.com> wrote:
>>
>>> http://cockpit-project.org/blog/cockpit-153.html
>>>
>>> Cockpit is the modern Linux admin interface. We release regularly. Here
>>> are the release notes from version 153.
>>>
>>>
>>> Add oVirt package
>>> -
>>>
>>> This version introduces the "oVirt Machines" page on Fedora for
>>> controlling
>>> oVirt virtual machine clusters.  This code was moved into Cockpit as it
>>> shares
>>> a lot of code with the existing "Machines" page, which manages virtual
>>> machines
>>> through libvirt.
>>>
>>> This feature is packaged in cockpit-ovirt and when installed it will
>>> replace
>>> the "Machines" page.
>>>
>>> Thanks to Marek Libra for working on this!
>>>
>>> Screenshot:
>>>
>>> http://cockpit-project.org/images/ovirt-overview.png
>>>
>>> Change: https://github.com/cockpit-project/cockpit/pull/7139
>>>
>>>
>>> Packaging cleanup
>>> -
>>>
>>> This release fixes a lot of small packaging issues that were spotted by
>>> rpmlint/lintian.
>>>
>>> Get it
>>> --
>>>
>>> You can get Cockpit here:
>>>
>>> http://cockpit-project.org/running.html
>>>
>>> Cockpit 153 is available in Fedora 27:
>>>
>>> https://bodhi.fedoraproject.org/updates/cockpit-153-1.fc27
>>>
>>> Or download the tarball here:
>>>
>>> https://github.com/cockpit-project/cockpit/releases/tag/153
>>>
>>>
>>> Take care,
>>>
>>> Martin Pitt
>>>
>>> ___
>>> cockpit-devel mailing list -- cockpit-de...@lists.fedorahosted.org
>>> To unsubscribe send an email to cockpit-devel-le...@lists.fedo
>>> rahosted.org
>>>
>>>
>>
>>
>> --
>> Marek Libra
>>
>> senior software engineer
>> Red Hat Czech
>>
>> <https://www.redhat.com/>
>> ___
>> cockpit-devel mailing list -- cockpit-de...@lists.fedorahosted.org
>> To unsubscribe send an email to cockpit-devel-le...@lists.fedo
>> rahosted.org
>>
>>
>>
>> ___
>> Users mailing list
>> Users@ovirt.org
>> http://lists.ovirt.org/mailman/listinfo/users
>>
>>
>
>
> --
>
> RYAN BARRY
>
> SENIOR SOFTWARE ENGINEER - TEAM LEAD - RHEV HYPERVISOR
>
> Red Hat NA <https://www.redhat.com/>
>
> rba...@redhat.comM: +1-651-815-9306 IM: rbarry
> <https://red.ht/sig>
>
> ___
> Devel mailing list
> de...@ovirt.org
> http://lists.ovirt.org/mailman/listinfo/devel
>



-- 

Marek Libra

senior software engineer

Red Hat Czech

<https://www.redhat.com>
___
Users mailing list
Users@ovirt.org
http://lists.ovirt.org/mailman/listinfo/users


Re: [ovirt-users] VM Portal looking for translators

2017-08-18 Thread Marek Libra
Hi Nicolás,

if you send me your Zanata's username, I can add you manually as translator
of VM Portal.

Thanks,
Marek


On Wed, Aug 16, 2017 at 8:40 PM, Nicolás <nico...@devels.es> wrote:

> Hi,
>
> Why do I see a red lock on the translation page claiming "This
> project-version is readonly. It cannot be edited"? Do I have to be granted
> access specifically on the language site to translate?
>
> (Not sure if related: Requested access to some language groups like
> described in [3], but it's still pending).
>
> Thanks.
>
> Nicolás
>
> El 14/08/17 a las 19:37, Jakub Niedermertl escribió:
>
> Hi all,
>
> new VM Portal project [1] - a replacement of oVirt userportal -  is
> looking for community translators. If you know any of
>
> * Chinese (Simplified)
> * French
> * German
> * Italian
> * Japanese
> * Korean
> * Portuguese
> * Russian
> * Spanish
>
> and want to join translation effort, please
>
> * sign up to Zanata translation environment [2]
> * request an access to language group of your choice [3]
> * and join us at [4]
>
> Thank you
>
> Regards
> Jakub
>
> [1]: https://github.com/oVirt/ovirt-web-ui
> [2]: https://translate.zanata.org
> [3]: https://translate.zanata.org/language/list
> [4]: https://translate.zanata.org/iteration/view/ovirt-web-ui/1.
> 2.0/languages
>
>
> ___
> Users mailing listUsers@ovirt.orghttp://lists.ovirt.org/mailman/listinfo/users
>
>
>
> ___
> Users mailing list
> Users@ovirt.org
> http://lists.ovirt.org/mailman/listinfo/users
>
>


-- 

Marek Libra

senior software engineer

Red Hat Czech

<https://www.redhat.com>
___
Users mailing list
Users@ovirt.org
http://lists.ovirt.org/mailman/listinfo/users


[ovirt-users] Announcing VM Portal 0.1.4

2017-04-20 Thread Marek Libra
Hello All,

Let me announce availability of the VM Portal v0.1.4 for preliminary
testing.
We are looking forward to your feedback which we will try to incorporate
into oncoming stable 1.0.0 version.

The VM Portal aims to be a drop-in replacement of the existing Basic User
Portal.
Revised list of Extended User Portal features will be implemented to
ideally replace it as well.

The VM Portal is installed by default since oVirt 4.1.

*The simplest way to try latest version is via Docker by [1].*
Once oVirt credentials are entered and initialization is finished, you can
access it on [2].

If you prefer to stay as closest to the production setup as possible, the
latest rpms are available on project's yum repo [3].
Then you can access the portal from [4].

Prerequisites: The VM Portal requires ovirt-engine 4.0+, so far mostly
tested on 4.1.

Please note, the docker image is so far meant to just simplify user testing
and is not ready for production setup.
Unless decided otherwise in the future, stable releases are still planed to
be deployed via rpms.

For issue reporting or enhancement ideas, please use project's github issue
tracker [5].

Thank you for your feedback,
Marek


[1] docker run --rm -it -e ENGINE_URL=https://[OVIRT.ENGINE.FQDN]/ovirt-engine/
-p 3000:3000 mareklibra/ovirt-web-ui:latest
[2] http://localhost:3000
[3] https://people.redhat.com/mlibra/repos/ovirt-web-ui
[4] https://[OVIRT.ENGINE.FQDN]/ovirt-engine/web-ui
[5] https://github.com/oVirt/ovirt-web-ui/issues


-- 

Marek Libra

senior software engineer

Red Hat Czech

<https://www.redhat.com>


​
___
Users mailing list
Users@ovirt.org
http://lists.ovirt.org/mailman/listinfo/users


Re: [ovirt-users] New User Portal - gathering feedback

2017-01-05 Thread Marek Libra
Please note, ovirt-4.1.0_beta2 is needed.
It contains recent ovirt-web-ui-0.1.1-2 release.

On Thu, Jan 5, 2017 at 9:57 AM, Marek Libra <mli...@redhat.com> wrote:

> Yes, recently just the OAUTH. We are working on fixing the docker image
> which was created before adding SSO support.
>
> On Wed, Jan 4, 2017 at 10:26 AM, Краснобаев Михаил <mi...@ya.ru> wrote:
>
>> Good day,
>>
>> just tried to run the new portal in docker, gives a "Login Failed" error.
>> I am running 4.0.5.
>> In engine.log i see:
>> 2017-01-04 11:04:11,692 ERROR [org.ovirt.engine.core.sso.utils.SsoUtils]
>> (default task-19) [] OAuthException access_denied: Cannot authenticate user
>> No valid profile found in credentials.
>>
>> Credentials that I tried "admin", "admin@internal-authz".
>> New portal works only with OAuth?
>>
>>
>> 03.01.2017, 22:51, "Michal Skrivanek" <mskri...@redhat.com>:
>>
>>
>> It doesn't hurt to add a link for the project page:)
>> Check out [1] for more details and also instructions for running a
>> standalone docker container plugged into existing setup. Should work fine
>> with any 4.0+
>>
>> Thanks,
>> michal
>>
>> [1] https://github.com/oVirt/ovirt-web-ui
>>
>> On 03 Jan 2017, at 18:15, Logan Kuhn <log...@wolfram.com> wrote:
>>
>>
>> I don't have a test cluster available for this at the moment, but could
>> you send some screenshots?  I'd like to get the resources and that might
>> help
>>
>> Regards,
>> Logan
>>
>> - On Jan 3, 2017, at 6:13 AM, Marek Libra <mli...@redhat.com> wrote:
>>
>> Hi,
>>
>> with ovirt-4.1.0_beta2, new Basic User Portal is introduced, so far as
>> tech preview.
>> To try, please follow the new "Basic User Portal" link from the main page.
>>
>> Recently most of previous (GWT based) Basic User Portal's functionality
>> is available.
>> In plan is full conformity and selected features of recent Extended
>> Portal.
>>
>> Following goals were stated for this project:
>> - improve UX by
>>   - modern UI (conforms Patternfly 3)
>>   - faster UI responses
>> - shareable
>>   - built from reusable components to share portions of the UI in other
>> projects (like ManageIQ)
>> - POC for ongoing oVirt UI development
>>   - one of the options for next-gen oVirt UI to consider
>>
>> From technical perspective, the project is based on
>> - oVirt REST API
>> - React/Redux/Saga
>> - Patternfly 3
>> - pure JavaScript App without server-side processing except the existing
>> REST API
>>
>> So far, the project is tech preview to gather user feedback.
>>
>> Please share your comments and ideas, it will really help with ongoing
>> development.
>> Real-life use-cases (both existing or potential) will be much appreciated.
>>
>> Thanks,
>> Marek
>>
>>
>> ___
>> Users mailing list
>> Users@ovirt.org
>> http://lists.ovirt.org/mailman/listinfo/users
>>
>> ___
>> Users mailing list
>> Users@ovirt.org
>> http://lists.ovirt.org/mailman/listinfo/users
>>
>> ,
>>
>> ___
>> Users mailing list
>> Users@ovirt.org
>> http://lists.ovirt.org/mailman/listinfo/users
>>
>>
>>
>> --
>> С уважением, Краснобаев Михаил.
>>
>>
>>
>> ___
>> Users mailing list
>> Users@ovirt.org
>> http://lists.ovirt.org/mailman/listinfo/users
>>
>>
>
___
Users mailing list
Users@ovirt.org
http://lists.ovirt.org/mailman/listinfo/users


[ovirt-users] New User Portal - gathering feedback

2017-01-03 Thread Marek Libra
Hi,

with ovirt-4.1.0_beta2, new Basic User Portal is introduced, so far as tech
preview.
To try, please follow the new "Basic User Portal" link from the main page.

Recently most of previous (GWT based) Basic User Portal's functionality is
available.
In plan is full conformity and selected features of recent Extended Portal.

Following goals were stated for this project:
- improve UX by
  - modern UI (conforms Patternfly 3)
  - faster UI responses
- shareable
  - built from reusable components to share portions of the UI in other
projects (like ManageIQ)
- POC for ongoing oVirt UI development
  - one of the options for next-gen oVirt UI to consider

>From technical perspective, the project is based on
- oVirt REST API
- React/Redux/Saga
- Patternfly 3
- pure JavaScript App without server-side processing except the existing
REST API

So far, the project is tech preview to gather user feedback.

Please share your comments and ideas, it will really help with ongoing
development.
Real-life use-cases (both existing or potential) will be much appreciated.

Thanks,
Marek
___
Users mailing list
Users@ovirt.org
http://lists.ovirt.org/mailman/listinfo/users


Re: [ovirt-users] Open in Full Screen

2016-05-04 Thread Marek Libra
The "Open in Full Screen" will be configurable via engine-config in 4.0 

- Original Message -

> From: "Colin Coe" 
> To: "users" 
> Sent: Friday, April 29, 2016 6:20:29 AM
> Subject: [ovirt-users] Open in Full Screen

> Hi all

> Is there a setting for globally turning on the console option of "Open in
> Full Screen"?

> Also, can the "Connect Automatically" be permanently and globally disabled?

> We're on RHEV 3.5.7

> Thanks

> CC

> ___
> Users mailing list
> Users@ovirt.org
> http://lists.ovirt.org/mailman/listinfo/users
___
Users mailing list
Users@ovirt.org
http://lists.ovirt.org/mailman/listinfo/users


Re: [ovirt-users] [ovirt-devel] Coming (Very) Soon - New ovirt.org Website & Deprecated Wiki

2016-02-18 Thread Marek Libra
Is old MediaWiki still running somewhere?

Thanks,
Marek

- Original Message -
> From: "Mikey Ariel" 
> To: users@ovirt.org, de...@ovirt.org, in...@ovirt.org
> Sent: Thursday, February 18, 2016 12:42:56 PM
> Subject: [ovirt-devel] Coming (Very) Soon - New ovirt.org Website &   
> Deprecated Wiki
> 
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA256
> 
> In the past months we've been working on upgrading the oVirt project
> infrastructure, to better support the community contributions.
> 
> One of the main platforms for our user documentation, release
> management content, and community content has been the MediaWiki site
> that you all know as ovirt.org. Most of us are familiar with the wiki
> site format, with all its advantages and disadvantages.
> 
> After several years of serving the community, I'm happy to announce
> that we are very near to completing a full upgrade of the website
> infrastructure from a wiki site to a static site, source-controlled on
> GitHub and authored in Markdown.
> 
> This email is the pre-launch announcement, as we are reaching the
> final stages of the migration, and there are a few actions that might
> affect your work on website content in the meantime.
> 
> Why migrate the website
> ===
> 
> As mentioned, wiki sites provide an open and flexible content editing
> platform. Unfortunately, as the site grows the content becomes quite
> difficult to manage and curate, resulting in lots of obsolete,
> outdated, and incorrect information.
> 
> By moving to a source-controlled repository and implementing GitHub's
> contribution workflow, we strive to ease the work of maintaining an
> up-to-date content site, employ a peer-review process for changes, and
> standardize the authoring markup language to lower the contribution
> barrier.
> 
> The Middleman framework (Ruby-based static site generator) was chosen
> based on observing successful implementation of other open-source
> community websites, such as OpenStack RDO, Project Atomic, and Gluster.
> 
> What we did so far
> ==
> 
> When we started the migration, our Web design team exported all of the
> wiki content from the old website and converted it to MD files. They
> also set up the website config flow, auto-deploy, and upgraded the
> look-and-feel of the website.
> 
> We then initiated a content review effort as well as a UX review for
> the new website in a smaller forum, which caught most of the critical
> issues with the new website and helped us get the new format to a
> place where we can release the website in a near-GA/public-beta format.
> 
> Yesterday (Wednesday Feb 17) we exported the website one more time and
> currently we're running a diff on all the files that changed since the
> initial export was done, to make sure we grab all the updates and the
> latest content before we launch the new website.
> 
> What is about to happen
> ===
> 
> Today we are initiating a **wiki freeze**, which means the old
> MediaWiki site will become read-only. This is to ensure that all of
> our diff scripts reflect the most current state of the content on the
> website, and that we don't lose any content in the transition.
> 
> Barring any unexpected blockers, we will port the ovirt.org domain to
> point to the new website and open the new website for contributions on
> **Monday February 22** or earlier.
> 
> What do you need to do right now
> 
> 
> If you have any wiki pages that you're actively editing, please don't
> save them to the old MediaWiki site, and hold onto your pending
> changes until we send the happy launch email.
> 
> We will also include instructions on how to contribute/edit/add
> content to the new website, but in general the workflow will be
> aligned with the standard GitHub best practices
> (clone-edit-commit-pullrequest), so you can utilize all of the git
> commands that you already know or work directly within the GitHub web
> editor.
> 
> 
> I'd like to thank all of the people who were involved with this
> migration so far, ovirt.org is a big website with lots of content and
> it was no small task to upgrade it.
> 
> Please feel free to ping me on- or off-list if you have any questions
> about the next steps, and expect a happy launch email soon!
> 
> Cheers,
> Mikey
> 
> 
> - --
> Mikey Ariel
> Community Lead, oVirt
> www.ovirt.org
> 
> "To be is to do" (Socrates)
> "To do is to be" (Jean-Paul Sartre)
> "Do be do be do" (Frank Sinatra)
> 
> Mobile: +420-702-131-141
> IRC: mariel / thatdocslady
> Twitter: @ThatDocsLady
> 
> 
> -BEGIN PGP SIGNATURE-
> Version: GnuPG v2
> 
> iQEcBAEBCAAGBQJWxa5AAAoJEHYPPTOszxHow10H/jeuhzMrUrPsCBedLg7OKnNh
> jdKDujT/aCyA4LgnRHnVBEASunShmVaOJrMdU4r0PZbdkX1Mf5/SvCEFGKY14qAg
> m/5CnDhlwbp5rqo09VOGLMg20CaMtpUoE1LpKE/epGYEKSBr2JIAA+HAsYa1OEyS
> 9oHDDx+ZIbfHNlygW1KpW6dsuZRscTbfy4kk8rY83YdJGyQiQN+ulsjT/c2N8ArR
>