Omer Frenkel has posted comments on this change.

Change subject: core, engine, webadmin: Initial support for alternative 
architectures
......................................................................


Patch Set 5:

(3 comments)

....................................................
File 
backend/manager/modules/dal/src/main/java/org/ovirt/engine/core/dao/VdsGroupDAODbFacadeImpl.java
Line 210:             
entity.setClusterPolicyName(rs.getString("cluster_policy_name"));
Line 211:             
entity.setClusterPolicyProperties(SerializationFactory.getDeserializer()
Line 212:                     
.deserializeOrCreateNew(rs.getString("cluster_policy_custom_properties"), 
LinkedHashMap.class));
Line 213:             
entity.setEnableBallooning(rs.getBoolean("enable_balloon"));
Line 214:             
entity.setArchitecture(ArchitectureType.forValue(rs.getInt("architecture")));
yes you are right, but even so i would prefer not to use the internal ordinal 
but a given id, look at other enums that implement Identifiable interface, like 
VmStatus
Line 215:             return entity;
Line 216:         }
Line 217:     }
Line 218: 


....................................................
File 
backend/manager/modules/utils/src/main/java/org/ovirt/engine/core/utils/ovf/OvfTemplateReader.java
Line 46:             
_vmTemplate.setOsId(osRepository.getOsIdByUniqueName(node.InnerText));
Line 47:         }
Line 48: 
Line 49:         // Workaround until the support for OVF on POWER is implemented
Line 50:         _vmTemplate.setArchitecture(ArchitectureType.x86_64);
yes on import we will check the template arch fetched from the os, against the 
cluster arch
Line 51:     }
Line 52: 
Line 53:     @Override
Line 54:     protected void readHardwareSection(XmlNode section) {


....................................................
File packaging/dbscripts/upgrade/03_03_0900_add_architecture_name_column.sql
Line 4: -- Existent clusters with cpu_name are x86_64, since alternative 
architectures are introduced after this upgrade
Line 5: UPDATE vds_groups SET architecture = 1 where cpu_name is not NULL and 
architecture = 0;
Line 6: 
Line 7: -- Update clusters
Line 8: create or replace FUNCTION __temp_update_vds_group()
ok but why do you update the cpu_name to be AMD G1 ? it doest sound right
Line 9: returns void
Line 10: AS $procedure$
Line 11: declare
Line 12: r vds_groups%rowtype;


-- 
To view, visit http://gerrit.ovirt.org/18938
To unsubscribe, visit http://gerrit.ovirt.org/settings

Gerrit-MessageType: comment
Gerrit-Change-Id: I1ecd642e2bc05067d55884c948bdaeb6e7838c26
Gerrit-PatchSet: 5
Gerrit-Project: ovirt-engine
Gerrit-Branch: master
Gerrit-Owner: Vitor de Lima <[email protected]>
Gerrit-Reviewer: Gustavo Frederico Temple Pedrosa 
<[email protected]>
Gerrit-Reviewer: Itamar Heim <[email protected]>
Gerrit-Reviewer: Leonardo Bianconi <[email protected]>
Gerrit-Reviewer: Michael Pasternak <[email protected]>
Gerrit-Reviewer: Michal Skrivanek <[email protected]>
Gerrit-Reviewer: Omer Frenkel <[email protected]>
Gerrit-Reviewer: Roy Golan <[email protected]>
Gerrit-Reviewer: Tomas Jelinek <[email protected]>
Gerrit-Reviewer: oVirt Jenkins CI Server
Gerrit-HasComments: Yes
_______________________________________________
Engine-patches mailing list
[email protected]
http://lists.ovirt.org/mailman/listinfo/engine-patches

Reply via email to