Academy and Foundation unixmens | Your skills, Your future
2.28K subscribers
6.66K photos
1.37K videos
1.24K files
6.06K links
@unixmens_support
@yashar_esm
[email protected]
یک کانال علمی تکنولوژی
فلسفه متن باز-گنو/لینوکس-امنیت - اقتصاد
دیجیتال
Technology-driven -بیزینس های مبتنی بر تکنولوژی
Enterprise open source
ارایه دهنده راهکارهای ارتقای سازمانی - فردی - تیمی
Download Telegram
دنبال واژه ها نگرد .
سنیور - جونیور و ...
سنیور کسی که بتونه راهکار ارایه بده . نه این که تجربه ۱۰۰ ساله داشته باشه .
سنیور کسی که بین چالش ها آنچه که نیاز سازمان هست را شناسایی و ارایه میده . ممکنه هزاران راهکار باشه ولی سنیور راهکار بهینه را انتخاب میکنه .

سنیور مثل یک کاراگاه هست . همیشه هوشیار و در حال مطالعه و دنبال دانش و راهکار ها
سنیور صبور هست
سنیور قابلیت این را داره که افراد را قانع کنه .
سنیور چشم انداز بیزینس را میدونه و سیگنال ها را درک میکنه .
سنیور بدنبال حل مشکلات هست .
سنیور میگه حل میکنیم نگران نباش و حل میکنه .
سنیور میتونه با هر تیمی خودش را آداپته کنه و این به معنی نادیده گرفتن ارزش هاش نیست .
سنیور صبوره .
سنیور تئوری را به عمل تبدیل میکنه .

سنیور تلاشش بهتر کردن دنیا است . جایی بهتر برای زندگی .
سنیور امید میسازه .
سنیور رفتار حرفه ای داره .
سنیور یه قهرمانه .


قدر سنیور های زندگی تون را بدونین
6
Media is too big
VIEW IN TELEGRAM
یک مکالمه خوب با ایلان ماسک .
مفاهیمی همچون کلود bci ,eeg و آینده جهان
#cloud #linux #eeg #bci
What’s hot in 3.3

OpenStack and oVirt: A match made in heaven

OpenStack has made a huge impact in the industry since its launch 3 years ago. It is one of the fastest growing, fastest improving open source projects on the planet, and there is a huge amount of interest in it as an Infrastructure as a Service provider. The oVirt project has been working to ensure that oVirt and OpenStack work well together. Like OpenStack, oVirt needs to be able to store VM images and snapshots, we need to configure multiple virtual LANs for multiple tenants, and we need a reliable, scalable storage back-end for persistent storage.

In oVirt 3.3, we have added integration with the Glance image storage service, allowing oVirt users to import images from Glance as disks for templates in oVirt, and to export VM templates and disks from oVirt to Glance, where they can be used to launch new instances on OpenStack.

We also leverage the Neutron service for the definition of VLANs, virtual routing and virtual NICs. oVirt can discover networks configured in OpenStack, and also use the oVirt management UI, via the Neutron APIs, to define network configurations.

More is planned for the future, as we work to make it easier to use oVirt for your scale-out workloads while continuing to use oVirt for traditional virtualized workloads where quality of service and high availability are critical.
Academy and Foundation unixmens | Your skills, Your future
oVirt 3.6 Release Notes | oVirt https://www.ovirt.org/develop/release-management/releases/3.6/
Experimental Docker Integration

oVirt Engine setup now provides experimental Cinder and Glance automated deployment using Docker

Cinder and Glance images are from kollaglue project. https://github.com/openstack/kolla kollaglue is ‘the official’ effort from openstack project to provide production-ready containers and deployment tools for operating OpenStack clouds. The kollaglue Docker images are built by the Kolla project maintainers. On oVirt side we have an optional plugin for oVirt engine-setup to pull and deploy their ready to use containers (glance and cinder only) and automatically adding them into your oVirt engine isntance.

Recently the cinder container setup for oVirt got broken cause they introduced the use of Ansible’s playbooks to customize and complete the container setup and unfortunately we are still not ready for that. You should be able to manually setup cinder with that containers following kolla documentation: https://docs.openstack.org/kolla/latest/

Glance container setup and its oVirt integration are still working.

Kolla images will not run on Fedora 22 or later currently. Fedora 22 compresses kernel modules with the .xz compressed format. The guestfs system in the CentOS family of containers cannot read these images because a dependent package supermin in CentOS needs to be updated to add .xz compressed format support