[ovirt-devel] Fwd: [ovirt-users] [FOSDEM][CFP] Virtualization & IaaS Devroom

[Sandro Bonazzola]

Sending to devel list as well, deadline is in 4 days.

-- Forwarded message -
Da: Piotr Kliczewski 
Date: mar 30 nov 2021 alle ore 14:54
Subject: [ovirt-users] [FOSDEM][CFP] Virtualization & IaaS Devroom
To: users 
Cc: Tal Nisan 


We are excited to announce that the call for proposals is now open for the
Virtualization & IaaS devroom at the upcoming FOSDEM 2022, to be hosted
virtually on February 5th 2022.

This year will mark FOSDEM’s 22nd anniversary as one of the longest-running
free and open source software developer events, attracting thousands of
developers and users from all over the world. Due to Covid-19, FOSDEM will
be held virtually this year on February 5th & 6th, 2022.

About the Devroom

The Virtualization & IaaS devroom will feature session topics such as open
source hypervisors and virtual machine managers such as Xen Project, KVM,
bhyve, and VirtualBox, and Infrastructure-as-a-Service projects such as
KubeVirt, Apache CloudStack, Foreman, OpenStack, oVirt, QEMU and OpenNebula.

This devroom will host presentations that focus on topics of shared
interest, such as KVM; libvirt; shared storage; virtualized networking;
cloud security; clustering and high availability; interfacing with multiple
hypervisors; hyperconverged deployments; and scaling across hundreds or
thousands of servers.

Presentations in this devroom will be aimed at users or developers working
on these platforms who are looking to collaborate and improve shared
infrastructure or solve common problems. We seek topics that encourage
dialog between projects and continued work post-FOSDEM.

Important Dates

Submission deadline: 20th of December

Acceptance notifications: 25th of December

Final schedule announcement: 31st of December

Recorded presentations upload deadline: 15th of January

Devroom: 6th February 2022

Submit Your Proposal

All submissions must be made via the Pentabarf event planning site[1]. If
you have not used Pentabarf before, you will need to create an account. If
you submitted proposals for FOSDEM in previous years, you can use your
existing account.

After creating the account, select Create Event to start the submission
process. Make sure to select Virtualization and IaaS devroom from the Track
list. Please fill out all the required fields, and provide a meaningful
abstract and description of your proposed session.

Submission Guidelines

We expect more proposals than we can possibly accept, so it is vitally
important that you submit your proposal on or before the deadline. Late
submissions are unlikely to be considered.

All presentation slots are 30 minutes, with 20 minutes planned for
presentations, and 10 minutes for Q

All presentations will need to be pre-recorded and put into our system at
least a couple of weeks before the event.

The presentations should be uploaded by 15th of January and made available
under Creative

Commons licenses. In the Submission notes field, please indicate that you
agree that your presentation will be licensed under the CC-By-SA-4.0 or
CC-By-4.0 license and that you agree to have your presentation recorded.
For example:

"If my presentation is accepted for FOSDEM, I hereby agree to license all
recordings, slides, and other associated materials under the Creative
Commons Attribution Share-Alike 4.0 International License. Sincerely,
."

In the Submission notes field, please also confirm that if your talk is
accepted, you will be able to attend the virtual FOSDEM event for the Q
We will not consider proposals from prospective speakers who are unsure
whether they will be able to attend the FOSDEM virtual event.

If you are experiencing problems with Pentabarf, the proposal submission
interface, or have other questions, you can email our devroom mailing
list[2] and we will try to help you.


Code of Conduct

Following the release of the updated code of conduct for FOSDEM, we'd like
to remind all speakers and attendees that all of the presentations and
discussions in our devroom are held under the guidelines set in the CoC and
we expect attendees, speakers, and volunteers to follow the CoC at all
times.

If you submit a proposal and it is accepted, you will be required to
confirm that you accept the FOSDEM CoC. If you have any questions about the
CoC or wish to have one of the devroom organizers review your presentation
slides or any other content for CoC compliance, please email us and we will
do our best to assist you.

Call for Volunteers

We are also looking for volunteers to help run the devroom. We need
assistance with helping speakers to record the presentation as well as
helping with streaming and chat moderation for the devroom. Please contact
devroom mailing list [2] for more information.

Questions?

If you have any questions about this devroom, please send your questions to
our devroom mailing list. You can also subscribe to the list to receive
updates about important dates, session announcements, and to connect with
other attendees.

See you all 

[ovirt-devel] Re: Can't find build.xml for ant

[Saif Abu Saleh]

Hi,

Look like this step is outdated as build got moved from ant to maven last
year

Note that this step is only to run the tests, if you just want to build the
project then you don't really need it.

I can't find similar profile for tests in maven, not sure if this step is
relevant anymore
+@Martin Perina 

Thanks,
Saif

On Sun, Dec 12, 2021 at 8:26 AM 천지환  wrote:

> Hi,
>
>
>
> i have trouble in 'ovirt-engine-extension-aaa-jdbc'
>
>
>
> when i follow the README.developer(
> https://github.com/jihwahn1018/ovirt-engine-extension-aaa-jdbc/blob/master/README.developer
> )
>
>
>
> i can't run '$ant check.IntegrationTest' because there is no build.xml
>
>
>
> where can i find it?
>
>
>
> Thanks,
>
> Jihwan
> ___
> Devel mailing list -- devel@ovirt.org
> To unsubscribe send an email to devel-le...@ovirt.org
> Privacy Statement: https://www.ovirt.org/privacy-policy.html
> oVirt Code of Conduct:
> https://www.ovirt.org/community/about/community-guidelines/
> List Archives:
> https://lists.ovirt.org/archives/list/devel@ovirt.org/message/LLK356QJXEWEKQQKK76MFAPBN7V56LRH/
>
___
Devel mailing list -- devel@ovirt.org
To unsubscribe send an email to devel-le...@ovirt.org
Privacy Statement: https://www.ovirt.org/privacy-policy.html
oVirt Code of Conduct: 
https://www.ovirt.org/community/about/community-guidelines/
List Archives: 
https://lists.ovirt.org/archives/list/devel@ovirt.org/message/IFL5E32GY766OPWYTQXE7VCTPUTT3VQI/

[ovirt-devel] Re: create a host using ssh

[Saif Abu Saleh]

Can you make sure that the SSH key is configured properly and authorized in
the host?


On Mon, Dec 13, 2021 at 10:19 PM Grace Chen  wrote:

> Hi Saif,
> I added it but got this error:
> ovirtsdk4.Error: Fault reason is "Operation Failed". Fault detail is
> "[Cannot add Host. Connecting to host via SSH has failed, verify that the
> host is reachable (IP address, routable address etc.) You may refer to the
> engine.log file for further details.]". HTTP response code is 409.
>
> On Thu, Dec 9, 2021 at 5:53 AM Saif Abu Saleh  wrote:
>
>> Hi,
>>
>> Can you try the following below?
>>
>> ssh_key = types.Ssh(public_key=my_ssh_key_string,
>> authentication_method=types.SshAuthenticationMethod('publickey'))
>> host = hosts_service.add_using_ssh(
>> types.Host(
>> name=name,
>> description='',
>> address=address,
>> port=22,
>> ssh=ssh_key,
>> cluster=types.Cluster(
>> name=cluster,
>> ),
>> ),
>> )
>>
>>
>>
>> Thanks,
>> Saif
>>
>> On Wed, Dec 8, 2021 at 6:28 PM Grace Chen  wrote:
>>
>>> I am writing a script to create a host using public ssh key
>>> the function I am using is add_using_ssh:
>>> my ssh_key is a an Ssh type already
>>> ssh_key = types.Ssh(public_key=my_ssh_key_string)
>>>
>>> host = hosts_service.add_using_ssh(
>>> types.Host(
>>> name=name,
>>> description='',
>>> address=address,
>>> root_password=None,
>>> port=22,
>>> ssh=ssh_key,
>>> cluster=types.Cluster(
>>> name=cluster,
>>> ),
>>> ),
>>> )
>>> When I choose from GUI, it doesn't ask me to put in root password, so I
>>> set it as None (Not sure if this is correct)
>>>
>>> I got error:
>>> ovirtsdk4.Error: Fault reason is "Request syntactically incorrect.".
>>> Fault detail is "For correct usage, see:
>>> ovirt-engine/apidoc#services/hosts/methods/add". HTTP response code is 400.
>>>
>>> looks like I didn't get all the parameters assigned?
>>> Can anybody help with this?
>>>
>>>
>>> ___
>>> Devel mailing list -- devel@ovirt.org
>>> To unsubscribe send an email to devel-le...@ovirt.org
>>> Privacy Statement: https://www.ovirt.org/privacy-policy.html
>>> oVirt Code of Conduct:
>>> https://www.ovirt.org/community/about/community-guidelines/
>>> List Archives:
>>> https://lists.ovirt.org/archives/list/devel@ovirt.org/message/MWDE4JADQRXCGYBH53BGJJTHCCU4H5UV/
>>>
>>
___
Devel mailing list -- devel@ovirt.org
To unsubscribe send an email to devel-le...@ovirt.org
Privacy Statement: https://www.ovirt.org/privacy-policy.html
oVirt Code of Conduct: 
https://www.ovirt.org/community/about/community-guidelines/
List Archives: 
https://lists.ovirt.org/archives/list/devel@ovirt.org/message/UE7JLO2HCM4S5JMSYZLK7RAXOTUMOCHD/

[ovirt-devel] Re: [OST] Documentation update needed

[Galit Rosenthal]

I have a patch which needs to be reviewed
https://gerrit.ovirt.org/#/c/ovirt-system-tests/+/117824/.

On Mon, Dec 13, 2021 at 12:56 PM Aviv Litman  wrote:

> Hi all, any updates ?
>
> Thanks!
>
> On Wed, Nov 24, 2021 at 3:31 PM Marcin Sobczyk 
> wrote:
>
>>
>>
>> On 11/24/21 13:54, Aviv Litman wrote:
>> > Hi All,
>> > I tried to follow the steps documented in oVirt System Tests Docs
>> > <
>> https://ovirt-system-tests.readthedocs.io/en/latest/CI/developers_info/index.html#on-your-laptop
>> >.
>> > After consulting with Marcin, I understand that we haven't use
>> > ./run_suite.sh  for a loong time now.
>> > I think the right command is for example:
>> > ./ost.sh run basic-suite-master el8stream
>> > --custom-repo=
>> https://jenkins.ovirt.org/job/ovirt-dwh_standard-check-patch/1346/
>> > 
>> >
>> > We don't know who maintains this docs.
>>
>> Anton, Galit, can we get rid of those outdated docs?
>> Either let's remove the server completely or redirect to current README.md
>>
>> Regards, Marcin
>>
>> >
>> > Thanks!
>> > --
>> >
>> > Aviv Litman
>> >
>> > BI Associate Software Engineer
>> >
>> > Red Hat
>> >
>> > alit...@redhat.com 
>> >
>> > 
>> >
>>
>>

-- 

Galit Rosenthal

SOFTWARE ENGINEER

Red Hat 

ga...@redhat.comT: 972-9-7692230

___
Devel mailing list -- devel@ovirt.org
To unsubscribe send an email to devel-le...@ovirt.org
Privacy Statement: https://www.ovirt.org/privacy-policy.html
oVirt Code of Conduct: 
https://www.ovirt.org/community/about/community-guidelines/
List Archives: 
https://lists.ovirt.org/archives/list/devel@ovirt.org/message/7TGQOBTULQXIKPIFIVK5LUX5AWSB6CE3/